31–40 of 52 posts
Excuse my ignorance but why does it look so complicated and unnecessary? What exactly does it improve over lets say PHP or Rails or whatever?
> What exactly does it improve over lets say PHP or Rails Uses the same code to render on server and in browser, enables moving render logic from browser to server and vice versa without doing a complete rewrite.
Earlier quoted context omitted.
Not quite sure what the big challenge is here. If the work is shifting to the server, you debug on the server! Read the logs. Attach a debugger. Instrument the code if you must! All that usual stuff. This is how web-development has been since the days of CGI. What am I missing?
And these days, you use the same browser debug tools to attach to nodejs.
Earlier quoted context omitted.
That's mostly because `create-react-app` was abandoned. There is no default project template for React SPA, so everyone just uses Next, even if they don't need SSR.
vite exists? what are you even talking about
Excuse my ignorance but why does it look so complicated and unnecessary? What exactly does it improve over lets say PHP or Rails or whatever?
> What exactly does it improve over lets say PHP or Rails Uses the same code to render on server and in browser, enables moving render logic from browser to server and vice versa without doing a complete rewrite.
Earlier quoted context omitted.
> What exactly does it improve over lets say PHP or Rails Uses the same code to render on server and in browser, enables moving render logic from browser to server and vice versa without doing a complete rewrite.
Why? lol
Earlier quoted context omitted.
on next.js first page loads are almost instant for very complex sites with very little work on the optimization side. it's an incredibly polished server and it does a lot of complex stuff to be so fast, but it's also well documented.
I don’t think this answers the parent question. Database queries still needs to be made and a view still needs to be rendered. What complexity does next.js solve?
in our case it solves performance, it actively keeps cache warmed up preventing it from ever serving a stale page or serving a non cached hit, preloads content for fast navigation, optimizes images, it's lightweight, scales horizontally, it's stable.
it has all the bells and whistles the big boys have, for free, you almost don't need to think about it, just follow some guidance.
while people say it's too much magic (there are 4 cache layers), you are always free to pop up the hood and read the documentation, which is excellent.
Earlier quoted context omitted.
It’s awful and I’m pretty sad that it seems the entire nodejs community has adopted next.js as standard. All projects I’ve been involved with use it and none of them use any SSR at all.
That's mostly because `create-react-app` was abandoned. There is no default project template for React SPA, so everyone just uses Next, even if they don't need SSR.
Excuse my ignorance but why does it look so complicated and unnecessary? What exactly does it improve over lets say PHP or Rails or whatever?
PHP is a programming language, Rails is a framework. They're quite different propositions. What you're seeing here is equivalent to poking around in the guts of Rails, which assuredly has plenty of complexity hidden inside it. I personally have a negative reaction to this amount of stuff in a project but I feel similarly about Rails.
Next’s big “thing” is one codebase that runs both on the server and client. That introduces complexity where you might not expect it. But a Rails app and a totally disconnected JS front end will also introduce complexity, just a kind you’re more familiar with.