Rob Cherny
Josh CollinsworthToday 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
Tyler Mumford@collinsworth Looks awesome! I'm going to read it.
Sara Joy 
@collinsworth oooooh... This looks like something I need to read. Thank you!
BD Cabrera@collinsworth That was really useful. Thanks so much for putting it together.
Samuel Plumppu@collinsworth Yeah, Svelte has been a huge improvement. Svelte 5 looks really promising too 😄
A lot has happened since 2019 when the latest major updates happened to Svelte too (since Svelte 4 mainly was a small upgrade)
Charlie ⚡️@collinsworth feel like i'm onboard with the sentiment, but i think i'd like to see, based surely on adoption, like react 19 or 20 just optimize react-dom.
i also just viscerally despise alex russell.
Gerardo Rodriguez@collinsworth Excellent post. Thanks for sharing!
Artem R 🇺🇦@collinsworth every time I see articles like this I’m checking state of JS, to see if I missed something big and how far it is detached with reality. In this case pretty far and quotes from incompetent hater Alex Russell does not help
William O'Connell@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.
Jon Lunman@collinsworth Wait... React *still* doesn't support web components? That was a deal breaker for me 4 years ago, but I thought for sure they'd have that solved by now. Yeesh.
Seb De Deyne@collinsworth Thanks for this, this was a good read!
I particularly agree with the critique on hooks (specifically useEffect, useMemo, and useCallback) and two-way binding.
The server-side rendering section looks off though. React has had SSR for ages (Next was always built on React SSR), it's React Server Components that's a new feature (which encompasses more than simply rendering a page on the server)
Would also love a more in-depth article on why you *should* use Svelte :)