Today I finally published a whopper of a post I've been working on for almost two months. I hope you enjoy it.

"Things you forgot (or never knew) because of React": https://joshcollinsworth.com/blog/antiquated-react

Things you forgot (or never knew) because of React

If you don't often look beyond established comfortable defaults, you might be surprised to learn just how far the world of frontend has moved away from React, and how big that gap continues to grow.

Josh Collinsworth

@collinsworth A few things in here confuse me:

"Every framework has coalesced around a hooks-like model for managing state" - what does "hooks-like" mean in this context? You mention Svelte stores, but I'm struggling to see in what sense those are the same thing.

In the server components part, hasn't Next.js been server rendering React for many years? Server components is (from my understanding) partial hydration, something much less common (though certainly not exclusive to React).

@williamoconnell I mean how frameworks used to have state very tightly coupled to specific components, as with React class components and the Vue options API.

Now, the model is more: extract only what you need modularly from the framework, and share it if/as needed between components.

And yes, I may be confusing server rendering and server components a bit. But in fairness, my reasoning is: Next support isn't necessarily React first-party support.