I used to wonder what was the play with pouring so much money into making a React framework the default. Now I understand the play
Next.js 15.1 is unusable outside of Vercel
61–70 of 113 posts
Re: Next.js 15.1 is unusable outside of Vercel
#62I 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?
The confusion is that there are plenty of front-end developers that have no clue what they are doing, and then blame it on the tool. Believe me, I interview plenty of front-end developers each month.
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 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.
Re: Next.js 15.1 is unusable outside of Vercel
#63I don't know. I felt NextJS got too complicated for me years ago and may have had a sweet spot back then when it felt magic. Now id just use a boring web server for most things. Chuck on a front end framework when needed for a SPA. If you choose classic or SPA things are far more simple.
people who were[0] "not even wrong" about understanding how an SPA maps naturally to the server-client boundary are now free to cook their fine pasta-based product however they think is best.
[0] still are ... ¯\_(ツ)_/¯
Re: Next.js 15.1 is unusable outside of Vercel
#64Don’t ever use Next. Terrible developer experience, vendor lock in, weird undocumented conventions that make building anything other than some kind of B2B SaaS CRUD site full of undocumented foot guns. My favorite thing I’ve encountered is the Next tag somehow dropping the FPS on a webgl scene on the same page to 2 FPS.
Did you pinpoint the issue, or are you just assuming it must be NextJs?
I work with NextJs, and RTF, and never encountered such problem.
Re: Next.js 15.1 is unusable outside of Vercel
#65Don’t ever use Next. Terrible developer experience, vendor lock in, weird undocumented conventions that make building anything other than some kind of B2B SaaS CRUD site full of undocumented foot guns. My favorite thing I’ve encountered is the Next tag somehow dropping the FPS on a webgl scene on the same page to 2 FPS.
Did you pinpoint the issue, or are you just assuming it must be NextJs? I work with NextJs, and RTF, and never encountered such problem.
The most confusing part is that it only happened really intensely on just one developer's machine.
I'll admit that the way we were using the image tag was a little unusual, but still something that was imminently supported by a plain HTML image tag.
My point is more that Next is such a bizarre black box that things like this were a regular occurrence.
To clarify: yes, it was the next Image tag. The moment we switched to using a plain image tag it resolved itself.
Re: Next.js 15.1 is unusable outside of Vercel
#66Earlier quoted context omitted.
I moved away from Next.js, and switched to Astro. Originally I just wanted to go back to basics, but didn't want to bother with having to set up all my routes, templating, serving static assets, build tasks. Astro just handles all that, and it's SSR by default. I also feel that Astro uses React/Vue as it was intended, as an interactive layer on top of HTML. It also made me realize how little I needed JS frameworks to…
I tried various astro sites, and as a user, a few things keep bugging me. - Visit their docs https://docs.astro.build/en/basics/astro-pages/ - Click `Routes` in the navigation Now: 1. There's a flicker in the content where the sidebar moves on the left 2. The title displays `docs.astro.build` for a split second before it says "Routing | Docs" Especially the second is quite annoying. I see it in every Astro site.
Here is one Astro site https://mayo.clumsy.fish/ with no flickers. Astro is pretty good but after trying RSCs I'm not going back.
Re: Next.js 15.1 is unusable outside of Vercel
#67vercel made a streaming metadata feature and add an option to opt-out (htmlLimitedBots). Is there anything else?
It made it by default. It's also not much of an "opt-out". An opt-out would be called "disableStreamingMetadata". Names convey intent, and it's obvious this is intended to be the behavior for all users with maybe an exception. The problem is that this is needed for a minuscule amount of users. This should've been an opt-in. The choice to make it opt-out is quite weird.
make sense now. They should add disableStreamingMetadata option to completely disable it instead of disabling it by matching user agent in a irreverent field name.
Many people choose Next.js because it has better SEO support than other options.
Re: Next.js 15.1 is unusable outside of Vercel
#68The FE community will do everything it can to avoid sending html to browser.
Re: Next.js 15.1 is unusable outside of Vercel
#69Don’t ever use Next. Terrible developer experience, vendor lock in, weird undocumented conventions that make building anything other than some kind of B2B SaaS CRUD site full of undocumented foot guns. My favorite thing I’ve encountered is the Next tag somehow dropping the FPS on a webgl scene on the same page to 2 FPS.
100%. Used it last year for the first time in a long time and was surprised by how awful the experience was. Docs were vague and hard to navigate. My web application seemed slow by default. We also had a hell of a time trying to deploy it with Docker to AWS using the sample Dockerfiles provided by Vercel (not sure if this is still the case).
Re: Next.js 15.1 is unusable outside of Vercel
#70I don't know. I felt NextJS got too complicated for me years ago and may have had a sweet spot back then when it felt magic. Now id just use a boring web server for most things. Chuck on a front end framework when needed for a SPA. If you choose classic or SPA things are far more simple.
I'm gonna go out on a limb and say most people who are building dynamic web applications don't need server-side rendering.