22 ms·
It's legit useful. Same language on the front and backend. Easily share dtos and libs across server/client. Able to render server side and/or client side. Same
by bottlepalm 4y ago
It's legit useful. Same language on the front and backend. Easily share dtos and libs across server/client. Able to render server side and/or client side. Same template logic on both (React). State is seamlessly transferred from server to client. The compiler creates optimal javascript bundles for every page on your site. SSR, SSG, ISR, CSR - are all options you can choose per page.
I've use almost most frameworks out there over decades, currently Next feels like the most productive. My wish list for it includes better static typing of api routes like trpc. A first class solution, like DI maybe for structuring backend code and accessing it via api or props.
- benatkin 4y ago> Same language on the front and backend. Yes, isomorphic JS. With React it can be annoying if you have a component that you never intended to run on the server and you get a hydration warning. It also complicates the decision of what language to use on the backend. It is often useful though.