71–80 of 168 posts
Totally off topic, and very much a nitpick, but Ling's Cars isn't a used car dealership, it's a car leasing firm. I care because I'm a fan :-)
Earlier quoted context omitted.
That's the luddite take. You probably shouldn't take up a career in technology if you're not willing to continually learn new things to keep up with advancements.
React may be an improvement on what came before, but it's still too complex for "draw a UI on the most-widely used platform." It's definitely not helping to democratize programming the way that the personal computer did when it simplified the world of computers down to a BASIC interpreter that a child could understand. The "advancements" are necessary, but let's be honest - they are far from ideal, overcomplicated me…
React is a lot simpler than all of the other frameworks/APIs/SDKs I've used like Cocoa/UIKit that draw a UI on a client that only a fraction of people can use. You'd expect it to be simpler, not more complicated, if you get to target a
Also, unlike iOS dev (for example), the web still has a trivial `echo "hello world" > index.html` you can use when you want it.
I always wonder how many web-client dev critics have done much work building clients on other platforms. Spoiler: it never was simple nor easy. And people's favorite hey day examples only worked for a specific platform.
Earlier quoted context omitted.
That's the luddite take. You probably shouldn't take up a career in technology if you're not willing to continually learn new things to keep up with advancements.
React may be an improvement on what came before, but it's still too complex for "draw a UI on the most-widely used platform." It's definitely not helping to democratize programming the way that the personal computer did when it simplified the world of computers down to a BASIC interpreter that a child could understand. The "advancements" are necessary, but let's be honest - they are far from ideal, overcomplicated me…
And taking a step back I think many people in frontend confuse React for a jQuery alternative, the thing you whip up a web project with by default, but it really isn't. That there is a component ecosystem might suggest its a jQuery alternative, but they really are for different scales of application programming.
I think it's this idea most harmful about React adoption and to be fair React marketing hasn't exactly said otherwise. So we get web pages with massive JS deps cause most people are probably using React for a productive developer experience rather than a fitting use case that actually justifies resorting to a virtual DOM model for applying view state, and yet React sold itself on "we probably know better than you about efficient DOM updates". That's true if you have lots of Juniors hanging around.
> What differentiates websites from one another today isn’t their underlying architecture but their content, design, and editorial. This is bad, this will kill the quirky, fun internet. Monoculture is not good.
No one seems to complain that all of the quirky websites use three.js. That doesn't seem so different to me.
Agreed! The intent of React is to drive new developers away from the building blocks of the web. And it has definitely succeeded at that. The way its ecosystem has grown all over the place, I find very passionate developers that swear by it. But you never know, every technology at some point of time becomes a luddite’s take and then it’d become hard to even consider React. Someday may be near as well, given that it’s…
That’s not React’s intent.
Earlier quoted context omitted.
The downside to that is that I've seen a lot of old school frontenders who 5-7 years ago were able to just dus html/css and sass haven't been able to keep up, it just got too complex. In that regard the old situation had better seperation of concerns.
That's the luddite take. You probably shouldn't take up a career in technology if you're not willing to continually learn new things to keep up with advancements.
Frontenders at the the time didn't see themselves as engineers.
Earlier quoted context omitted.
"there's nothing in between training wheels (CRA) and a motorcycle" AFAIK the "betweens" are Next.js, Blitz.js, Gatsby, Remix, Expo, etc.
I like Next.js quite a bit but I don't need SSR. To expand upon my use case a bit: I need a way to create dozens of small SPAs in an enterprise environment maintained by people who are not front-end experts. CRA fits the bill almost perfectly except it makes certain Webpack/Babel configs unavailable that make my life very difficult. The token response from the CRA team tends to be: we don't think you need this, fork…
Can't you switch Next.js to SSG for all routes since v9?
Earlier quoted context omitted.
> With every other framework, even though the core framework is capable enough, it feels like I have to reinvent wheels, axles, and more. Curious, does that apply to Angular/Ember?
Agreed. As someone unfamiliar with the JS ecosystem I find React to be difficult because it appears just as a UI library. I have to then choose between dozens of competing options for everything (local state management, API calls, forms, URL routing, etc) where as frameworks such as Ember (not sure about Angular) seem to provide those features out of the box using a consistent API as well as some structure. I guess R…
for all of these examples, React offers a vanilla way to do this, or you could use React + ECMAScript & polyfills to do this. there are definitely bolt-on libraries that do more with those but you can be fine with minimal dependencies on other things.
I feel like a lot of pain with React development is self-inflicted.
Earlier quoted context omitted.
Agreed. As someone unfamiliar with the JS ecosystem I find React to be difficult because it appears just as a UI library. I have to then choose between dozens of competing options for everything (local state management, API calls, forms, URL routing, etc) where as frameworks such as Ember (not sure about Angular) seem to provide those features out of the box using a consistent API as well as some structure. I guess R…
> I guess React is powerful in the sense that it will allow you to do this that wouldn't fit well with the structure and way of doing things of Ember/Angular, but that seems to be a relatively rare problem. I think that might depend on what you're trying to do. I'm guessing as you say you are unfamiliar with the JS ecosystem, that you were trying to do something relatively simple. As a full-stack developer who does a…
I'm not a js developer, but picking libraries based on popularity seems a dubious idea if a sufficient number of other people are doing the same.