I attribute react's problems to 2 things: not including state management in the lib, not deprecating old APIs for like concerns when updating major versions. I prefer Svelte or Vue.
If React had bundled state management, it would have been bad, it would have run hard afoul of your second concern, would never have been deprecateable, it would have been an anchor they could never cut loose. React would have been doomed.
People keep wanting React to be more (like this whole post) but I feel like smart in the know people all recognize what an incredible boon it is that React targeted a specific problem, that it engaged the community to find & work through solutions to other orthogonal concerns. React has been free to evolve, and these other orthogonal concerns have been free to evolve & shake out.
At this point, there's a couple pretty stable, well known, well respected answers to any orthogonal concern. Switching between them is not that bad, they all have a deliberate architecture & practice you can move towards that makes internal sense. React doesn't care.
People's desire to make React care & intertwine it's concerns is really confounding & weird to me. But it's easy to blog about, it's easy to spread some dissent. It's harder to write a good paean for what a correct, amazing, better than everyone-elses-attempt this was by the React team.
I loved what the team did with Flux. They talked about it, made it sound simple as heck, then told us to go implement it ourselves. We had all sorts of goes & attempts before React released their state management system. We had independent thought, we had many ideas, where-as if Facebook had just dropped Flux right away, shortly after release of React, we'd all just be a bunch of sheep & never have seen other ideas or explored the notion. Having a healthy group diversity around ideas, to support technical ecosystems is so bloody important, and this post & the desire to see concerns all bundled with one another to make it easy & thought-free, to get everyone following the same easy-path, they just sounds so wrong & short-sighted to me. They ignore to me the most powerful aspect of mankind: what amazing explorers we are, how great our vision & ability to see.
People keep wanting React to be more (like this whole post) but I feel like smart in the know people all recognize what an incredible boon it is that React targeted a specific problem, that it engaged the community to find & work through solutions to other orthogonal concerns. React has been free to evolve, and these other orthogonal concerns have been free to evolve & shake out.
At this point, there's a couple pretty stable, well known, well respected answers to any orthogonal concern. Switching between them is not that bad, they all have a deliberate architecture & practice you can move towards that makes internal sense. React doesn't care.
People's desire to make React care & intertwine it's concerns is really confounding & weird to me. But it's easy to blog about, it's easy to spread some dissent. It's harder to write a good paean for what a correct, amazing, better than everyone-elses-attempt this was by the React team.
I loved what the team did with Flux. They talked about it, made it sound simple as heck, then told us to go implement it ourselves. We had all sorts of goes & attempts before React released their state management system. We had independent thought, we had many ideas, where-as if Facebook had just dropped Flux right away, shortly after release of React, we'd all just be a bunch of sheep & never have seen other ideas or explored the notion. Having a healthy group diversity around ideas, to support technical ecosystems is so bloody important, and this post & the desire to see concerns all bundled with one another to make it easy & thought-free, to get everyone following the same easy-path, they just sounds so wrong & short-sighted to me. They ignore to me the most powerful aspect of mankind: what amazing explorers we are, how great our vision & ability to see.