I used nextjs for the last year building a static site, then a SPA. I didn't use it in a server side rendering case. Whenever people talk about build time rendering, the first question is if the data is specific to the user or not. If it is specific, like anything beyond the login page and some marketing landing pages, the build time rendering doesn't apply.
Tech Lead/Team Lead. Senior WebDev.
Intermediate Grade on Computer Systems-
High Grade on Web Application Development-
MBA (+Marketing+HHRR).
Studied a bit of law, economics and design
Location
Spain
Education
Higher Level Education Certificate on Web Application Development
Of course that non-crawable paths are out of the equation. But there is a different use-case, when you've data which is public but logged in users see the content customised or more capabilities.
On the other hand Next help you with image optimization, pre-loading internal linked views, caching things up and the view presented is -usually- Interactive faster, so the user experience will be better anyway.
But there is a different use-case, when you've data which is public but logged in users see the content customised or more capabilities.
Agreed, I just don't usually work on apps that have this component.
Also, I think the nextjs/blitzjs zero API approach is somewhat novel (and I assume this is what people like the most), but it goes against my general lack of enthusiasm for isomorphic applications. I think inertia.js is a nice technology agnostic approach to achieving similar goals though.
I used nextjs for the last year building a static site, then a SPA. I didn't use it in a server side rendering case. Whenever people talk about build time rendering, the first question is if the data is specific to the user or not. If it is specific, like anything beyond the login page and some marketing landing pages, the build time rendering doesn't apply.
Of course that non-crawable paths are out of the equation. But there is a different use-case, when you've data which is public but logged in users see the content customised or more capabilities.
On the other hand Next help you with image optimization, pre-loading internal linked views, caching things up and the view presented is -usually- Interactive faster, so the user experience will be better anyway.
Agreed, I just don't usually work on apps that have this component.
Also, I think the nextjs/blitzjs zero API approach is somewhat novel (and I assume this is what people like the most), but it goes against my general lack of enthusiasm for isomorphic applications. I think inertia.js is a nice technology agnostic approach to achieving similar goals though.
I remember reading about this one. That is nice.