Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Next.js 15.1 is unusable outside of Vercel

omarabid.com

Post reply on HN
Print view View original

21–30 of 113 posts

Re: Next.js 15.1 is unusable outside of Vercel

#21

Post by zackify »

Aeolun wrote: post #16

Next has become a joke. It’s mildly frustrating that with Remix’s inexplicable transformation into react-router, there’s few great react frameworks left (for me), I’m back to plain vite with tanstack router.

I’m surprised this post is able to stay up on hackernews.

One time I simply made a post about how a page was simpler to code and understand in Remix.

You may not believe this but I had 3+ chat requests from multiple employees at vercel.

Across multiple social media accounts. All asking to take it down or meet and discuss with them.

Re: Next.js 15.1 is unusable outside of Vercel

#22

Post by christophilus »

koakuma-chan wrote: post #15

Everybody should be talking about how it takes Next.js 10 seconds to compile a route in development mode. Rust compiler is smoking in the corner.

It’s unusable. The worst devx I’ve experienced since… dunno.

I can’t think of a stack I’ve worked with that I loathed more since that one and only time looked at helping someone fix their Sharepoint site.

Re: Next.js 15.1 is unusable outside of Vercel

#24

Post by cianuro_ »

zackify wrote: post #21
Aeolun wrote: post #16

Next has become a joke. It’s mildly frustrating that with Remix’s inexplicable transformation into react-router, there’s few great react frameworks left (for me), I’m back to plain vite with tanstack router.

I’m surprised this post is able to stay up on hackernews. One time I simply made a post about how a page was simpler to code and understand in Remix. You may not believe this but I had 3+ chat requests from multiple employees at vercel. Across multiple social media accounts. All asking to take it down or meet and discuss with them.

What a poor approach to try and protect the brand.

Re: Next.js 15.1 is unusable outside of Vercel

#25

Post by Illniyar »

jasoncartwright wrote: post #9

Post suggests the underlying problem is the metadata takes too long to put in the HTML? A few tags? Really? This kind of problem, and the vendor lock-in, is completely unimaginable for any web framework I can think of. Bizarre.

I think it was that if metadata requires getting data from third parties or something, it takes a long time, and it doesn't affect what the user sees.

It did say this was a problem for very few people.

Re: Next.js 15.1 is unusable outside of Vercel

#26

Post by dimitrisnl »

woutr_be wrote: post #10
dimitrisnl wrote: post #2

Oof. I'm sure Vercel might patch this issue. But I had had enough of these little annoyances. For example, the documented way to identify prefetches in the middleware has been broken for weeks (months?). A lot of small issues that keep adding up. I'm not going to shill something else here, but I have a bit of Next.js fatigue lately. Still love the JS ecosystem though. Anyway, thanks for bringing this up!

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.

Re: Next.js 15.1 is unusable outside of Vercel

#28

Post by jowday »

Don’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.

Re: Next.js 15.1 is unusable outside of Vercel

#29

Post by tonyhart7 »

icemelt8 wrote: post #23

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?

maybe because you did not use that much of serverless function that vercel natively support

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

Re: Next.js 15.1 is unusable outside of Vercel

#30

Post by Illniyar »

iw7tdb2kqo9 wrote: post #6

vercel 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.

Post reply on HN