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

91–100 of 113 posts

Re: Next.js 15.1 is unusable outside of Vercel

#91

Post by pas »

darajava wrote: post #72
pas wrote: post #52

Earlier quoted context omitted.

because they pushed shiny new features that are reaaaallly good for a certain set of commercial users (think webshops, where time to first contentful paint equals time to money) and the tech is not bad, it's just meh (immature and a bit misguided) after all by flipping the whole thing upside down, defaulting to server-side, a lot of previously hard problems became easy (the usual glueing of different APIs - user, CMS…

Can you suggest alternatives? I've used Next and Svelte[kit] in prod and have been very unhappy with both.

Can you name/explain your problems with them? What was the intended use case and goals, what did you like about them, and what you didn't, and what was something that was definitely missing for you?

Re: Next.js 15.1 is unusable outside of Vercel

#92

Post by shoeb00m »

aitchnyu wrote: post #48
jowday wrote: post #28

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.

How was Vercel able to frog-boil normal React users with vendor lock-in? React was supposed to be Meta's baby and open source was supposed to defeat vendor lock-in.

Because create-react-app was awful

Re: Next.js 15.1 is unusable outside of Vercel

#93

Post by consumer451 »

6ak74rfy wrote: post #87

What's the recommend full-stack setup, if not NextJS? My background: I have ~15 years of software development experience, but practically all of it in backend stuff. (Well, I did some AngularJS a decade ago but that's it.) So, when I recently wanted to build a fullstack app for the first time for a side project, I looked around and learnt NextJS was the way to go. (Gemini said that, then Cline's official documentatio…

What are you building? I am working on a classic SaaS webapp, and I have found that using React/Refine.dev/Vite has been great. Refine.dev let me focus on my features, and not basic CRUD page stuff.

Re: Next.js 15.1 is unusable outside of Vercel

#94

Post by const_cast »

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.

We've gone so far that the promise of a simple scripting language like JS has multiple build and compile steps, and they're taking longer than a god damn C++ compiler.

Who knew that if we just threw Clang in a browser we'd somehow have a more pleasant experience?

On a related note, we use PHP at work. Same fucking problem. It's a scripting language, should be painless no? Wrong. PHP has awful performance characteristics, so we need to generate some code ahead of time. So we have a custom build step that uses Composer. That custom build step is SLOW. Probably because it was created by shitty PHP programmers and not the people who wrote GCC.

Re: Next.js 15.1 is unusable outside of Vercel

#95

Post by koakuma-chan »

whoisyc wrote: post #80
aitchnyu wrote: post #48

Earlier quoted context omitted.

How was Vercel able to frog-boil normal React users with vendor lock-in? React was supposed to be Meta's baby and open source was supposed to defeat vendor lock-in.

They exert immense influence over the React ecosystem, even its documentation. Example: https://react.dev/learn/creating-a-react-app If you are new to React and just figuring out how to get it running, you will likely end up on this page. The first recommendation is Next.js. The real best way for a beginner to start is IMO Vite. Comes with everything you need to get started and lets you choose what to do next. Curiou…

> They exert immense influence over the React ecosystem, even its documentation.

Not necessarily, it's just (sadly) the best React framework out there.

Why is no one building a better framework?

Re: Next.js 15.1 is unusable outside of Vercel

#96

Post by thdxr »

Panchitous wrote: post #86

It’s opinionated, and they’ve been pushing streaming—just like the React team—right? Yes. Is it unusable outside of Vercel? No. As far as I know, Next works without hiccups if you deploy to containers. However, that’s not our case, as we use Lambdas on AWS. We’ve been using OpenNext since the early versions. I must add that I’ve followed a lot of libraries on Discord, and among all those I’ve joined (PayloadCMS comin…

what did i do to you!?

Re: Next.js 15.1 is unusable outside of Vercel

#97

Post by pfych »

ggregoire wrote: post #89
6ak74rfy wrote: post #87

What's the recommend full-stack setup, if not NextJS? My background: I have ~15 years of software development experience, but practically all of it in backend stuff. (Well, I did some AngularJS a decade ago but that's it.) So, when I recently wanted to build a fullstack app for the first time for a side project, I looked around and learnt NextJS was the way to go. (Gemini said that, then Cline's official documentatio…

If you don't need server rendering, I'd just recommend React without framework, and Vite [1] to run the app in dev and build the app in prod, then host the build (basically a HTML page with a JS file) on AWS S3 or similar static hosting platforms. That's the solution I've been using for 10+ years without any problem. For the backend you can use whatever you are comfortable with. I mostly use PostgREST [2] nowadays. I…

This is the way to go for 99.9% of React apps, I've been using a similar setup for almost 7 years now.

Plain React, Vite, React-Router, & SWR. Is simple & works great for almost every use case.

Re: Next.js 15.1 is unusable outside of Vercel

#98

Post by winstonp »

koakuma-chan wrote: post #95
whoisyc wrote: post #80

Earlier quoted context omitted.

They exert immense influence over the React ecosystem, even its documentation. Example: https://react.dev/learn/creating-a-react-app If you are new to React and just figuring out how to get it running, you will likely end up on this page. The first recommendation is Next.js. The real best way for a beginner to start is IMO Vite. Comes with everything you need to get started and lets you choose what to do next. Curiou…

> They exert immense influence over the React ecosystem, even its documentation. Not necessarily, it's just (sadly) the best React framework out there. Why is no one building a better framework?

It's called TanStack Start

Re: Next.js 15.1 is unusable outside of Vercel

#99

Post by joquarky »

bravesoul2 wrote: post #58
Illniyar wrote: post #25

Earlier quoted context omitted.

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.

That's "deprecating EKS for Omega star at the end of the month" level of dumb. Let the programmer do high latency shit if they want. Give them a damn catch if they need it.

Still waiting on support for ISO timestamps...

Re: Next.js 15.1 is unusable outside of Vercel

#100

Post by koakuma-chan »

winstonp wrote: post #98
koakuma-chan wrote: post #95

Earlier quoted context omitted.

> They exert immense influence over the React ecosystem, even its documentation. Not necessarily, it's just (sadly) the best React framework out there. Why is no one building a better framework?

It's called TanStack Start

No RSC support
Post reply on HN