|
jquery and react don’t really do the same thing? seems funny to compare them except as "popular JavaScript things" also you can totally use react without a node toolchain, just plop in a script tag
|
# ? Apr 4, 2019 02:06 |
|
|
# ? Dec 8, 2024 09:16 |
|
Vue is better for that React assumes you use jsx
|
# ? Apr 4, 2019 03:23 |
|
everything is bad
|
# ? Apr 4, 2019 03:26 |
|
vue is nice enough for the simple ltittle poo poo I’ve built with it. is google web toolkit (GWT) still a thing or did that die with Java 1.5 and generics?
|
# ? Apr 4, 2019 03:49 |
|
animist posted:typescript's type system is stupidly powerful. honestly i've never used another language with nicer unions: you are like a little baby, watch this it's kind of hosed up how good typescript is
|
# ? Apr 4, 2019 04:20 |
|
akadajet posted:you know. like a tesla teslajs would make a great name for a new js framework
|
# ? Apr 4, 2019 06:53 |
|
redleader posted:teslajs would make a great name for a new js framework A really expensive one you can pretend is an environmental choice?
|
# ? Apr 4, 2019 06:54 |
|
dick traceroute posted:A really expensive one you can pretend is an environmental choice? plus it regularly explodes, kills bystanders, or drives into nearby firetrucks metaphorically, of course
|
# ? Apr 4, 2019 07:00 |
|
akadajet posted:angular 7 works just fine of course its not on the fifth backwards-incompatible version of its router, like react, so i guess it makes people worry about their job security or some such
|
# ? Apr 4, 2019 07:04 |
|
hot take: state management in react is in fact terrible and redux and hooks are quite literally golang levels of bad
|
# ? Apr 4, 2019 07:07 |
|
https://mobile.twitter.com/babaisyou_/status/1110991655816122373
|
# ? Apr 4, 2019 07:13 |
|
Sagacity posted:hot take: state management in react is in fact terrible and redux and hooks are quite literally golang levels of bad Oh yeah talking of, since work pivoted and my job search has not been successful yet I've been a full time golang developer for more than a month now. Actually not too bad for small applications, as our sophistication is growing though we're really starting to feel the lovely tooling though. Eg the lack of a vendoring solution. Lots of copy pasting. Go modules are 100% mandatory, now they exist I lead the charge on some -400k loc prs to remove vendored dependencies like lol whoever thought that was a good solution Because we're not really trying for much code reuse I'm not feeling the lovely type system as bad as I thought I would. it'd be nice to have proper unions though for domain modeling
|
# ? Apr 4, 2019 07:20 |
|
Feisty-Cadaver posted:vue is nice enough for the simple ltittle poo poo I’ve built with it. one app team actually moved to gwt within the last few years. I mean yeah they moved from some desktop VB gui garbage (that iirc had hard session binding so "we've run out of dB connections" was a regular occurence) but still, why not move to literally anything else?
|
# ? Apr 4, 2019 07:39 |
|
pokeyman posted:jquery and react don’t really do the same thing? seems funny to compare them except as "popular JavaScript things" they do different things but i've never run into a case where i had to use them at the same time quote:also you can totally use react without a node toolchain, just plop in a script tag it's been a while since i tried that, but iirc it ran like dog poo poo. idk though, the bottleneck might have been something else
|
# ? Apr 4, 2019 09:25 |
|
A couple of months ago I did a full test applications in Angular 7, React with Redux and Vue.js for PoC for moving from a V1 frameworks. It all really depends on what you're trying to do in the end. For us Angular 7+ is the best fit because we're looking at a client application not a website, 30 developers, long development timescales and continuous work and rework on components. If you're making a 1 shot website or web app with a small team I would say React, ditch Redux. If you're doing something non-commercial then try Vue. The documentation for all of them is terrible. Any competent developer will be able to bash together something in any of them relatively quickly. It's all about your use cases and ongoing maintenance plan.
|
# ? Apr 4, 2019 10:24 |
|
how much of an improvement is angular 7? it would have to be pretty goddamn significant to make me stop thinking angular is an unusable trash fire
|
# ? Apr 4, 2019 11:18 |
|
DaTroof posted:how much of an improvement is angular 7? it would have to be pretty goddamn significant to make me stop thinking angular is an unusable trash fire No idea, I've not used any of the previous Angular2+ versions. One of my colleagues thinks it's a massive improvement over AngularJS. You just have to make some choices at the start to avoid it going out of control, like we'll use Directives this way, our Router config will be this, our Forms will be that etc. Our intention is to rewrite 200K+ lines of JS into a new Angular app and it looks like it'll work for that.
|
# ? Apr 4, 2019 11:28 |
|
Aramoro posted:No idea, I've not used any of the previous Angular2+ versions. One of my colleagues thinks it's a massive improvement over AngularJS. You just have to make some choices at the start to avoid it going out of control, like we'll use Directives this way, our Router config will be this, our Forms will be that etc. Our intention is to rewrite 200K+ lines of JS into a new Angular app and it looks like it'll work for that. this is pretty sound advice for any software project isn't it?
|
# ? Apr 4, 2019 11:32 |
|
Boiled Water posted:this is pretty sound advice for any software project isn't it? yes, but a good framework will guide you towards the correct decisions by default (pit of success etc.) while a bad framework will have seventeen ways to do the same thing and leave you with no documentation to help you figure out which one won’t be deprecated in a year
|
# ? Apr 4, 2019 11:53 |
|
Boiled Water posted:this is pretty sound advice for any software project isn't it? It is, but for some reason people seem to have less design discipline when doing web apps in my experience. Probably because JS is garbage so doing anything that works is fine.
|
# ? Apr 4, 2019 11:56 |
|
Js frameworks that force my colleagues to stop using lovely hoisted vars as globals are a good thing. Now we import a singleton Vue instance to every file instead
|
# ? Apr 4, 2019 12:01 |
|
ctps: My job position was just renamed from "Software engineer" to "Researcher" Guess I was just too terrible?
|
# ? Apr 4, 2019 12:03 |
|
angular 7 is 6 better than angular 1. that’s quite a lot better!
|
# ? Apr 4, 2019 12:18 |
|
q: does redux actually do anything??? like im trying to test it out and i can't even figure out what im supposed to do with it e: posting on POS page
|
# ? Apr 4, 2019 15:03 |
|
HoboMan posted:q: does redux actually do anything??? yeah. it does state management and pumps up your slocs
|
# ? Apr 4, 2019 15:28 |
|
I like Vue, at least for the little bit I've used it. Seems relatively straight forward and a little more light-weight compared to the other big frameworks. Plus I get to sit around being while everyone argues about Angular vs React. Of course, if you want to skip javascript you could just compile Rust to wasm. Sapozhnik posted:Also make sure you use TypeScript and Parcel in your project as well.
|
# ? Apr 4, 2019 15:50 |
|
Sapozhnik posted:you are like a little baby, watch this
|
# ? Apr 4, 2019 15:59 |
|
pseudorandom posted:Of course, if you want to skip javascript you could just compile Rust to wasm. my former coworker was making a framework for this. also a javasript to rust converter. bless his heart.
|
# ? Apr 4, 2019 16:01 |
|
HoboMan posted:also a javasript to rust converter. what??
|
# ? Apr 4, 2019 16:03 |
|
Sapozhnik posted:it's kind of hosed up how good typescript is, compared to JavaScript, and average, compared to other, decent languages fixed
|
# ? Apr 4, 2019 16:06 |
|
CPColin posted:fixed typescript has a better tooling/typesystem quality combo than any other language, change my mind
|
# ? Apr 4, 2019 16:11 |
|
Considering typescript is just Microsoft trying to make javascript be more like C#..
|
# ? Apr 4, 2019 16:27 |
|
typescript's type system is significantly above and beyond c#. it's basically Anders Hejlsberg's playground for wacky ideasanimist posted:typescript has a better tooling/typesystem quality combo than any other language, change my mind https://twitter.com/garybernhardt/status/1007690864909529088?s=21 bernhardt is good at explaining things, but he's also that most tedious form of "optimize your life" nerd
|
# ? Apr 4, 2019 16:43 |
|
Sagacity posted:hot take: state management in react is in fact terrible and redux and hooks are quite literally golang levels of bad correct, don't use either of those things
|
# ? Apr 4, 2019 16:43 |
|
this is such a bullshit comparison
|
# ? Apr 4, 2019 16:44 |
|
Sapozhnik posted:this is such a bullshit comparison don't worry about it too much, he's got some weird hangups to say the least
|
# ? Apr 4, 2019 16:46 |
|
but also: apps are slow and i hate it.
|
# ? Apr 4, 2019 16:58 |
|
yeah gently caress redux, at first it feels like needless complexity for its own sake, but the react architecture is so loving terrible it really does need something like redux or it ends up being less maintainable than without redux.. but I can't shake the feeling that a well organized hierarchy of js files could get you to the same place without all the extra bullshit. I am a really terrible js programmer, though, so please correct me if I'm wrong (I'm prob very wrong)
|
# ? Apr 4, 2019 17:14 |
|
I have not yet come to a solid conclusion about whether Redux is a good or bad thing overall. I think I haven't used it properly yet. It's good because it means in theory nearly all the state for your entire application can be kept in a single data structure operated on by a strictly defined collection of possible actions. This is amazingly easy to unit test. Meanwhile, because they have no internal state, your components become incredibly simple (in a lot of cases, functional) which likewise is insanely easy to test. This feels like an improvement over the state of the application being distributed across every component instance in the application, and it means that if a thing happening in one component needs to affect something in another component, it's very easy to make that happen. It's bad because the connector component which links the React component to Redux is relatively complex and annoying to test. The song-and-dance around defining all of your actions up front and then carefully instantiating and dispatching them feels very boilerplatey and, as mentioned, increases the codebase size. It also makes it harder to produce a reusable component which can be consumed by third parties - do they have to rig up an identical state object in order to use it? Or do they have to reproduce the whole interface between the component and the state store themselves? There might be workarounds for these. There might be other bad things I haven't run into yet or which I'm forgetting.
|
# ? Apr 4, 2019 17:52 |
|
|
# ? Dec 8, 2024 09:16 |
|
yeah i am also a v terrible javascript programmer, but i got the sense that adding redux wasn't really doing anything except adding a bunch of boilerplate that makes my code hard to read in exchange i get... a state machine i mostly had to make myself?
|
# ? Apr 4, 2019 18:16 |