3 ms·
> As someone who just decided to learn React (and modern javascript, after 1.5 decades or so of not programming in javascript at all Sorry you're experiencing
by pcthrowaway 4y ago
> As someone who just decided to learn React (and modern javascript, after 1.5 decades or so of not programming in javascript at all
Sorry you're experiencing this. It's not "just React" though, it's pretty much all Javascript (or Typescript) now. Especially front-end, but I swear, JS/TS on the front or back is like trying to learn to drive a car in heavy traffic while also repairing the brake lines which are malfunctioning
- keyle 4y agoSaying it's not "just React" is normalising the problem, which I think really doesn't benefit React trying to set itself as the de-facto standard for front-end code.
- epolanski 4y agoDe facto what...? Maybe if you only read Twitter. There's tremendous amount of work in other libraries too. I would also argue that poor web standards support hinders the future of React, especially for web components.
- deleted 4y ago[deleted]
- joemi 4y agoI love your analogy. That's definitely how it's felt for me.
- SCLeo 4y agoIt is also not just JavaScript, but also with current AI technologies, which arguably, change even faster than JavaScript. You see, fast changing technology does not imply the underlying tech is bad, but rather there are unexplored new ideas and there are enough interested people ready to dive right in. Yes, it is exhausting to follow. Yes, it is frustrating when the floor shifts underneath you. However, dismissing a tech just because it is fast changing is not a good altitude.
- TheCleric 4y agoGoing to train an AI to write JavaScript frameworks.