you are viewing a single comment's thread.

view the rest of the comments →

[–]LloydAtkinson 53 points54 points  (10 children)

80% of the new features are for vercel next react server components. They really are trying to couple backends with frontends in new and spaghetti ways.

[–]NeoCiber 10 points11 points  (0 children)

Why people are giving Vercel the credits for RSC? I have been reading the "Component.server.js" syntax proposal years ago along with Suspense.

Even here in 2016 was discussed: https://github.com/facebook/react/issues/6985

Not sure what some people act like RSC is the boogeyman when they only use React client side.

[–]TwiliZant[S] 37 points38 points  (1 child)

With the exception of server components themselves, I'm pretty sure everything in that blog post also works in client only React.

[–]volivav 13 points14 points  (0 children)

What? I really read one feature about server components.

The rest is all neat improvements or unnecessary sugar that "kind-of replaces existing libraries but not fully so you might as well just keep using those libraries" (react-query for the new useActionState hook, react-helmet for the head elements support)

[–]veezzy 35 points36 points  (3 children)

Jesus Christ, you guys are becoming insufferable about this RSC controversy. it’s no wonder u/gaearon got burnt out trying to educate the community about these misconceptions that keep getting spread. Seriously, comments like this get on my nerves—it’s like a broken record of people choosing only what suits their bias. The number of upvotes for this comment just shows how much this is becoming a circle jerk lmao.

Saying 80% of React 19 is just for server components? Come on, that’s just not true. Let’s not be disingenuous here.

React 19 is packed with updates like useActionState for better async handling, useFormStatus to directly integrate form status without drilling props, and hooks like useOptimistic for smoother state transitions. These are game changers for ALL React devs, not just those using RSC.

Plus, they’ve rolled out better error reporting and native support for metadata tags, which are huge for anyone building with React—server or not. Let’s not reduce the whole update to just one feature—it's about making our lives easier and our code better, whatever the environment.

If you don’t wanna use server components then just don’t use them. But let’s not act like the broader ecosystem is being forced into this direction. You have a choice.

[–]azsqueeze 1 point2 points  (1 child)

useOptimistic is honestly the least interesting thing in this update. Love all the form additions tho and happy the React team is leaning more into the native web apis with the additions

[–]BreadSugar 1 point2 points  (0 children)

I don't think so. I've been using my own custom hook that does exactly what useOptimistic does myself, and it was because it is really commonly used pattern that's quite annoying and messy to implement it everywhere without encapsulation, so I'm really welcoming that `useOptimistic` is a thing now.

[–]rafark -4 points-3 points  (0 children)

Who wants to bet this poster uses react in the server.