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

31–40 of 113 posts

Re: Next.js 15.1 is unusable outside of Vercel

#31

Post by jowday »

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.

Lee Robinson from Vercel is gonna show up in this thread as soon as he wakes up, don’t worry.

Re: Next.js 15.1 is unusable outside of Vercel

#32

Post by aj_g »

christophilus wrote: post #22
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.

For real. It makes me feel like I'm coding in C++ again. I have the suspicion that many Next aficionados are using M12 Macs with 512GB RAM and don't know how bad the DX is on anything less than a bleeding edge machine.

Re: Next.js 15.1 is unusable outside of Vercel

#33

Post by koakuma-chan »

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?

It's hard to get Next.js to build because it runs your code during build time, and it has some obscure DynamicError shit, I barely got it to work somehow.

Re: Next.js 15.1 is unusable outside of Vercel

#34

Post by csomar »

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.

You should write about that? Good thing I am out of the social media sites these days.

Re: Next.js 15.1 is unusable outside of Vercel

#35

Post by sali0 »

Next and RSCs have become some of the most frustrating things I've worked with on frontend. Dealing with FE is already annoying enough, but having to wrestle the magic of Next and then vendor lock-in to Vercel to top it off.

Team is trying out Tanstack router + vite this week. Excited to build a regular ass CSA.

Re: Next.js 15.1 is unusable outside of Vercel

#37

Post by tisdadd »

dimitrisnl wrote: post #12
drag0s wrote: post #4

Earlier quoted context omitted.

I'm still using Next.js in my work and projects because I still think it may be the best way to ship React to production, but it used to be something fun, enjoyable and productive. sometimes I feel a bit sad about the direction it's going in since the move from pages to the app router.

The best way to ship React to production is with Vite. It opens up tons of options (Tanstack, RR, Simple SPA, whatever) and you don't even bring the hosting provider into the discussion.

This - I spent quite some time fighting the new Next.js conventions not working for me making a legit web app instead of traditional site, switched to vite and was like yay, things work again and so fast. Normally I am all about embracing the framework, but kept thinking for what was happening I could use PHP instead and host anywhere.

Re: Next.js 15.1 is unusable outside of Vercel

#38

Post by koakuma-chan »

tonyhart7 wrote: post #36
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.

rust compiler actually do compiling, are you sure that next js compiler do the same thing?

It's mostly running Vercel spyware.

Re: Next.js 15.1 is unusable outside of Vercel

#39

Post by Bengalilol »

Illniyar wrote: post #25
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.

Implementing an option in order to stream metadata would have been more smart. Am I missing something obvious ?

Re: Next.js 15.1 is unusable outside of Vercel

#40

Post by nonninz »

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 not sure if you are implying that you aren't using remix anymore after the rebranding, or that it's not a framework anymore?

Because React Router 7 definitely works as a framework [1] and it works like a charm.

Source: Backend developer with 15 years experience, lately switched to full stack, using RR7 after advice from a very good friend, still getting amazed every day.

[1] https://reactrouter.com/start/framework/installation

Post reply on HN