> once you learn the shape they expect
replyI’m reminded of this essay discussing frameworks versus libraries [0].
I’ve been saying for years we need CCR (Client Centric Rendering).
replyWhat we do is have the server just serve the page and let the client handle most of the rendering.
It’s novel and innovative
Isn't this html + javascript?
replySmells like SPA
replyAm I missing something? The entire point of next.js is that it's backend+frontend in one project
replythat’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.
replynextjs 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.
replyNextjs is also a bundler for web applications. And it deploys the front end assets.
replyIt'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.