4 ms·

There’s a great deal of value in the “fullstack meta-frameworks” model of things. For one, using the same language on the backend and frontend is underrated fea

There’s a great deal of value in the “fullstack meta-frameworks” model of things. For one, using the same language on the backend and frontend is underrated feature. But Next.js is not the only option on the market, so I partially echo your sentiment, not around React SPA vs React fullstack, but around Next.js vs a half dozen better alternatives for the React ecosystem.

root_axis 2y ago
> using the same language on the backend and frontend is underrated feature. You don't need a framework for that.
shepherdjerred 2y ago
> using the same language on the backend and frontend is underrated feature I agree, but you can definitely do this without SSR or Next.JS. Common examples are tRPC, Zodios, or even just plain fetch calls with shared type definitions. - https://trpc.io/ https://trpc.io/ - https://www.zodios.org/ https://www.zodios.org/
- root_axis 2y ago
  Even SSR is pretty easy to do without a framework. Just render the component with react-dom/server and use hydrate on the client.