Hoping this marks the beginning of the end for React. Finally, the web world can move on to something sensible: WASM, web components, or (god forbid) serving HTML to browsers again.
In a way its popularity has done a lot of harm for the progress of the web. The way they dragged their heels on web components was akin to Apple's suppression of PWAs. And its ubiquity in web development means developers are bloating what should be tiny websites with miniscule functionality instead of only for it when it's actually needed. Our other analogy here is the kubernetes fallacy, most teams genuinely don't need it but will go through pains to put it in place and take on exorbitant overheads for no good reason. I don't necessarily completely agree with the premise stated in the article that portrays it as a success story.
LLM-generated article at least partially.
Hoping this marks the beginning of the end for React. Finally, the web world can move on to something sensible: WASM, web components, or (god forbid) serving HTML to browsers again.
In a way its popularity has done a lot of harm for the progress of the web. The way they dragged their heels on web components was akin to Apple's suppression of PWAs. And its ubiquity in web development means developers are bloating what should be tiny websites with miniscule functionality instead of only for it when it's actually needed. Our other analogy here is the kubernetes fallacy, most teams genuinely don't need it but will go through pains to put it in place and take on exorbitant overheads for no good reason. I don't necessarily completely agree with the premise stated in the article that portrays it as a success story.
This. Reactive web was a horrible step for accessibility
Meta is giving React $600,000 per year.
That enough for ……. 2 developers!
or 10-20 outside of the US.