> Many of today's most polished products, like Linear and ChatGPT launched as Ne...

jeremy_k · on Feb 21, 2025

The data layer is an orthogonal choice to the frontend framework / library.

You could use Next.js + any API to create an application.

You could use Next.js + a sync engine to create an application.

You could use React Router + Vite + any API to create an application.

You could use React Router + Vite + a sync engine to create an application.

krashidov · on Feb 21, 2025

Isn't next.js a full stack framework though? Like can't you have it do server side rendering? https://nextjs.org/docs/app/building-your-application/data-f...

matijash · on Feb 21, 2025

Full-stack is an overloaded term, but it used to mean "a completr solution for building a web app."

From the comment above: Next.js is the opposite of a "batteries included" framework. No abstractions for ORM, background jobs, sending emails, managing attachments, web socket communication - all very basic stuff when dealing with a production application.

hombre_fatal · on Feb 22, 2025

Next.js solves the hard thing of server rendering + frontend hydration of JS components.

So if that's the battery that you need, pretty much nothing else has it except for Next.js.

These days, I tend to want a web framework to do the hard things for me rather than the tedious/boilerplate but simple things like email-sending.

krashidov · on Feb 22, 2025

Right so if you built your own sync engine why would you use next.js?

hombre_fatal · on Feb 26, 2025

Well, if you went so far as to reimplement Next.js, I don't think you're using Rails either.

And frankly I'd like to see it since that's a really hard problem to just roll your own solution. And probably a huge waste of time if you're trying to ship a real product on top of it.