[rjbwork]

Can you elaborate on this please?

I'm a backend engineer with little interest in the frontend morass de jure, but my company is looking to move to React. Reasons are that Vue2 is being EOL and there's a lot of work to move to Vue3, it's about the same workto just start over in React and there's a larger pool of talent for it.

I don't really know much about the whole situation, but it seems to highlight the cause of my general disinterest in the ecosystem. Would be nice if you could shed some light on it.

[WhiteBlueSkies]

I tried to elaborate in a previous comment(on some other post) but moderation deleted my comment. It's very difficult to hide disgust and disdain for this library if you've used it. The reasons are as follows:

1) React boasts that is just JS but has arbitrary rules like don't use useEffect in loops.

2) Even after 9 years even the core features are not clearly explained. The authors clearly did not know what they were doing.

3) There is no in-depth treatise of the library anywhere. A tweet here and a tweet there or some blog posts which you can't even figure out if they are outdated. If you visit the docs you'll see the most trivial examples because anything more complicated and now you are neck deep in trouble due to state menagement.

4) See this: https://news.ycombinator.com/item?id=34142168. It's a mystery if useEffect is for side-effects or not. If you use any other well-documented library you will see things clearly explained in the docs. With React it's just hype based woo-woo. It is responsible for degrading web development into plug-and-play style of poorly written components glued together because the core idea is just bad.

[dieselgate]

I get the impression parent comment was being a bit sensationalist. React has pros and cons but people generally wouldn’t remove react in favor of jquery (or something else). You mentioned a very valid case of beginning to use react - it’s commonly used and works