News for hackers. Stuff that matters.
Re:New React docs pretend SPAs don't exist anymore by andrewstuart on Saturday March 18, 2023 @03:38AM (#35206996)
I don’t want server side react.

It’s disappointing to me they’ve gone so hard on server side.

Re:New React docs pretend SPAs don't exist anymore by MartijnHols on Saturday March 18, 2023 @06:36AM (#35207873)
For most React apps, SSG is by far the best option. With Next.js it’s easy to do and takes less effort than a client-side app with a separate backend. SSR React was a PITA initially 2-3 years ago, but it, libraries and the frameworks have come a long way.
Re:New React docs pretend SPAs don't exist anymore by NerdiOrg on Saturday March 18, 2023 @07:25AM (#35208122)
Nobody is forcing you to use all the capabilities. You can still use it for client-side only if you want, but the efficiency of having both is perfect for me personally and our company.
Re:New React docs pretend SPAs don't exist anymore by synergy20 on Saturday March 18, 2023 @12:50PM (#35210699)
frontend is already complex enough, there are many use cases do not need SSR at all, React used to be SPA first, now is SSR first(just like svelte), which means lots of unnecessary stuff to understand for SPA programmers. I came from vue-svelte-react, now Vue is the only one still does true SPA(SSR is opt-in), so, I am back to Vue and hope it won't change to SSR-first like the rest.

React is owned by Meta which cares more about SSR, similar to Svelte. Vue is not owned by any single company, that seems like a huge huge plus now.

Re:New React docs pretend SPAs don't exist anymore by nextaccountic on Saturday March 18, 2023 @02:07PM (#35211560)
> now Vue is the only one still does true SPA(SSR is opt-in),

With next.js, SSR is opt-in too