Switching to Svelte could be a massive W for a small organization, they'll get inundated with a flood of highly motivated, skilled ex-React developers. Also if react is as probablamitc as people say (I'm veteran of the Angular/Angular.js transition wars so i don't know whats going on as much). If svelt et co. it helps a business not only achieve greater speed but maintenability long-run it's a competative advantage and should be exploited. much like how legacy c code is being handled due to its memory unsafeness. Would that happen?

Last tidbit Web Components are often suggested as a solution, they could lead to another layer of complexity. For instance, how do we manage complex, shared state across different web components that might be built with different tools like Lit or Stencil? How do components built by different systems pass information to each other without essentially creating an ad-hoc framework on top of the web components standard?

A lot of the issues stem from the fact that Meta was backing React for so long (before it got purchased by Vercel), so it always had a ton of resources dedicated to it which helped win the mindshare. It's like that saying, "No one ever got fired for picking Oracle" or however it goes.

The other frameworks (except for Angular) are simply too small when compared to the massive coffers backing React. I mean, Vue is by no means small at this point, there are hundreds of contributors and people are making good livings off of the donations Vue receives, but it's still nowhere near React levels where Meta's full-time salaried employees got paid to work on React. It's a blessing and a curse to be a FOSS framework like Vue.