3 ms·
Vercel and co managed to mangle the one benefit you mentioned. They introduced the concept of a "server component": one that is rendered once and cannot update
by BoorishBears 3y ago
Vercel and co managed to mangle the one benefit you mentioned.
They introduced the concept of a "server component": one that is rendered once and cannot update state.
And instead of making that opt-in, they made it the default.
—
That is to say, the default of React is to no longer allow updating state in components.
No value proposition is safe from the forces of financially incentivized thought leaders.
- leerob 3y agoThe Meta team introduced Server Components: https://legacy.reactjs.org/blog/2020/12/21/data-fetching-with-react-server-components.html https://legacy.reactjs.org/blog/2020/12/21/data-fetching-wit...
- BoorishBears 3y agoThe RFC was driven by Vercel. Vercel announced RSC landing in experimental on stage before the React team even updated their docs I'm not even going to get into how ridiculous it is that the default config chosen was to break people's builds for a feature that isn't mature enough to have anything more than a single reference implementation from Vercel.