I still dont understand the lie, that its difficult to host next.js.
I am hosting several nextjs apps for my day job. We just put them in a docker and throw them on the server, whats the confusion?
I am hosting several nextjs apps for my day job. We just put them in a docker and throw them on the server, whats the confusion?
lets be real here, vercel did not maintain next js for a "free lunch" they want people that use next js be the customer of vercel
For example if you stay as close as possible to the framework defaults, everything is golden. But as soon you start pushing it to the limits the cracks start to appear.
Last year I was working on a NextJS app with 15k files, 18k unit tests, 100+ developers in the same repository and a page with hundred of millions of page views daily. Under that conditions NextJS doesn't scale, but again, those conditions are not the majority of the NextJS cases.
In that project, we have been using NextJS as a standalone for around 5 years and each time NextJS rollout a major version it take us at least 2 months to be able to upgrade and keep it working.
The main problem is that building a website is very different than programming a web application.
As a senior software engineer with a Masters degree in CS, NextJS works great for me.
Another poster here claims an <Image> drops his Three.js to 2 fps, and of course blames it on NextJS. I work with Three.js, and never seen such issue (React-three-fiber however does have some peculiarities). Before blaming some random tool, maybe first investigate where the problem lies. If you pinpointed it to NextJS, sure, it's NextJS. Before that, don't blame anyone but yourself.
I always laugh when I read HN and Lobster commenters. I use NextJS and LLM's, and I leave my competitors in the dust. So yeah, the proof is in the pudding, not in some random folks commenting on the internet.
This also reminds me of some commenter here on HN who was angry at Java because their sorting function was unstable for many years :D.
And besides, just because using <img> instead of <Image> doesn't imply that the actual issue was in <Image>, it might also be in another part and <Image> triggered it. As I told you, as long as you don't pinpoint the problem, you can't say where the problem lies.
Maybe your definition of pinpointing is different than mine.
Instead of being cowards, please reply what features of Next do not work in self hosting through a simple 1 line Docker image?