I think that React is actually doing something that it was never really intended to in the first place …
… also React which said hey keep your state management system but will manage all of the view state for you and the only reason why React had any state management system at all was because each component could be a smart component …
… React was never meant to be the state manager and then we got hooks and hooks were close enough to being a state management system where we kind of looked over the fundamental flaws …
The bulk of that video pits SolidJS against React.
Interestingly Soild's project founder Ryan Carniato joined EBay's Marko team in 2020.
Unlike mainstream front end frameworks Marko was designed back in 2013 to focus on server side capabilities first - and by 2017 also included client-side VDOM. Now Marko is integrating client-side reactive capabilities as an alternative to client side VDOM (Marko: Designing a UI Language) - with partial rehydration intact. Mainstream frameworks tend to "bolt on" SSR after the fact - Marko is a server side solution that "bolted on" (and integrated) client-side rendering.
Another perspective I recently ran across, in particular:
The bulk of that video pits SolidJS against React.
Interestingly Soild's project founder Ryan Carniato joined EBay's Marko team in 2020.
Unlike mainstream front end frameworks Marko was designed back in 2013 to focus on server side capabilities first - and by 2017 also included client-side VDOM. Now Marko is integrating client-side reactive capabilities as an alternative to client side VDOM (Marko: Designing a UI Language) - with partial rehydration intact. Mainstream frameworks tend to "bolt on" SSR after the fact - Marko is a server side solution that "bolted on" (and integrated) client-side rendering.
For a pro-hooks examination see: React Hooks: Has React Jumped the Shark?