Yea I've been coding every framework under the sun since the 90s and I'm pretty happy with Next.js at the moment. It can render on the server and re-render on t

Yea I've been coding every framework under the sun since the 90s and I'm pretty happy with Next.js at the moment. It can render on the server and re-render on the client with the same framework, same language, same functions. Statically typed server to client and back to server. JSX/TSX has no strange template syntax and again static type checking. Compiling automatically tree shakes, bundles, code splits per route. I can do SSG, SSR, CSR, ISR. I can specify per route/api caching strategies. I can host serverless or self host. I'm knocking websites out left and right. It feels like I'm building a single application not two separate frontend/backend applications; managing overhead rendering and communicating between them. Next.js, Nuxt, Remix, SvelteKit - are all part of this next generation batteries included frameworks that can seamlessly transition from server side rendering to client side interactivity. $('.getResults').on('click', () => { $.ajax({ url: '/api/results', data: { foo: 'bar' }, success: function (result) { $('.results').html(result); } }); }); I mean look at this unmanageable bug prone code from the blog post. Nothing here is safe, no way to validate the classes where the data is coming from/going to. No validation of the api or its parameters. If you scaled this example you'd end up with nightmare level code. Yea I've been there already, I'm not going back.