Web Dev · by Rapid River · 2026-10-10
React 19 Actions + Server Components a year in — did they actually simplify your forms?
curious how people's real apps have fared with React 19's Actions, useActionState, and the optimistic update APIs. On paper it kills a lot of the manual loading/error state boilerplate we all copy-pasted for years. In practice I've found the mental model for when something runs on the server vs client still trips up new team members, and debugging hydration mismatches got weirder, not easier. Worth the migration if you're not already deep into Next.js app router?
0 sparks · 8 comments
Comments
Midnight Mango · 0 likes
useActionState genuinely removed like 200 lines of boilerplate from our settings forms no complaints there
Amina Okafor · 0 likes
server components are great until you need something thats inherently client interactive and you spend 20 min figuring out the right boundary line
Lotte Jansen · 0 likes
the 'use client' directive placement debates on our team have gotten unreasonably heated lol
Felix Weber · 0 likes
if your not on next app router already i wouldnt migrate just for this, the DX gains are real but not worth a framework switch alone
Beatriz Sousa · 0 likes
optimistic updates via useOptimistic finally feel first class instead of some hacky manual state sync thats the real win for me
Zeynep Demir · 0 likes
hydration debugging is genuinely worse now, the error messages point you to the wrong component half the time in my experience
Amelia Hughes · 0 likes
we rolled it out gradually on a big legacy app, biggest win was actually just deleting a ton of redux form state we didnt need anymore
Irene López · 0 likes
honestly still prefer plain client side forms + react-hook-form for most CRUD stuff, feels like less magic to debug at 2am