It’s like next.js but for backend.
Personally not for me. These are very productive once you learn the shape they expect.
But the wheel needs to be reinvented on how to do everything.
I ran have straight forward verbose code with no hidden control flow
> once you learn the shape they expect
I’m reminded of this essay discussing frameworks versus libraries [0].
[0] https://tomasp.net/blog/2015/library-frameworks/
I’ve been saying for years we need CCR (Client Centric Rendering).
What we do is have the server just serve the page and let the client handle most of the rendering.
It’s novel and innovative
Smells like SPA
Isn't this html + javascript?
Am I missing something? The entire point of next.js is that it's backend+frontend in one project
that’s likely the promise but it’s so confusing and high cognitive overhead to maintain that backend <-> frontend relationship. ‘use client’ - i think the special sauce for why people use nextjs is all frontend based. the frontend that comes from the backend.
nextjs dx is a special kind of hell. disclaimer: im just a simple rails guy.
Next.js is a poor choice for a client-side application. It is first and foremost a server-side framework, and trying to force it to be client-side is to work against it. There are so many better options than Next.js for dedicated client-side front-ends.
Nextjs is also a bundler for web applications. And it deploys the front end assets.
It's yet another backend framework, added that it only runs on vercel infrastructure.
There are better front end and back end servers, those that simply rely on nodejs to serve. Next.js does that, without vercel.