-
"This gives us the best performance characteristics when you're following best practices (i.e. hoist data fetches to Server Components or route loaders), at the expense of making an already bad pattern a bit worse." [1]
Their rational was pretty solid in the PR, but seems they overestimated how ready the community is to embrace newer best practices and are back tracking.
[1] https://github.com/facebook/react/pull/26380
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
-
Shutout for Svelte. It took the best of VUE and react. It's fast and very lightweight when compared to Vue, which has a largish ecosystem.
https://svelte.dev/
-
- SolidJS (fine-grain, fastest, most consistent) (dx similar to react) (small ecosystem)
[1] https://www.solidjs.com/
-
I use React like the V in MVC for my homemade framework:
https://github.com/williamcotton/williamcotton.com/blob/3719...
That’s a link to a route handler (controller) that makes a graphql call (model) and then explicitly updates the DOM with renderComponent (view).
FWIW, that code runs both client-side and server-side and it is written in F# that compiles to both environments.
-
> React was originally designed to be the V in MVC.
So much this. As we built more sophisticated apps using React we were constantly frustrated with how much code was ending up in the views, and how difficult controller frameworks were to work with (looking at you Redux). So we built our own mini-framework that explicitly separates the view from the controller. Seems like a simply change but it is amazing how much more productive it makes developers, especially with large complex applications that need refactoring as they evolve.
Unfortunately our skills are in writing code, not marketing, so we don't have a fancy website like most frameworks. But the details are here: https://github.com/aha-app/mvc
