←back to thread

Next.js is infuriating

(blog.meca.sh)
1033 points Bogdanp | 5 comments | 02 Sep 25 06:57 UTC | HN request time: 0.944s | source
Show context
YuukiRey ◴[02 Sep 25 10:04 UTC] No.45101009[source]▶
I 100% agree. I've ran into the same issues, and I would never use Next.js for anything, and I will encourage every team at work to use something else.

In general Next.js has so many layers of abstraction that 99.9999% of projects don't need. And the ones that do are probably better off building a bespoke solution from lower level parts.

Next.js is easily the worst technology I've ever used.

replies(16): >>45101028 #>>45101139 #>>45101375 #>>45101378 #>>45102069 #>>45102103 #>>45102427 #>>45102810 #>>45102903 #>>45103225 #>>45104004 #>>45104045 #>>45105250 #>>45110734 #>>45112201 #>>45126685 #
jbreckmckye ◴[02 Sep 25 11:00 UTC] No.45101378[source]▶
My experience with Next.js are that its rough edges are a feature, not a bug. Everything is geared towards you giving up and just using Vercel's hosting
replies(9): >>45101858 #>>45102115 #>>45102304 #>>45102325 #>>45102348 #>>45102563 #>>45102608 #>>45102624 #>>45111217 #
Imustaskforhelp ◴[02 Sep 25 12:40 UTC] No.45102348[source]▶
Which is why I actually love sveltekit considering that its really easy to self host it / host it anywhere serverless. I hosted it on cloudflare. Though I do feel that everyone is pushing nextjs in the llm space and llm's are more comfortable with next instead of sveltekit but they can still do some mind boggling things in sveltekit and I love them while using sveltekit itself
replies(1): >>45102432 #
1. tommica ◴[02 Sep 25 12:48 UTC] No.45102432[source]▶
Svelte is financed by vercel, so who knows if sveltekit drifts in the same direction.
replies(2): >>45102869 #>>45102981 #
2. Imustaskforhelp ◴[02 Sep 25 13:30 UTC] No.45102869[source]▶
Yes I know but the way I see sveltekit is that there are adapters for cloudflare etc. and I doubt how sveltekit can drift into such direction without immense blacklash

I don't know much about the nextjs and whether it was open like sveltekit currently is.

To me, nextjs (I think) was always meant to favour vercel but sveltekit has a rich history of managing multiple adapters.

Now, that being said there are still some chances of a rugpull that might happen but if that ever happens, I am staying on the last sveltekit that worked with cf and other cloud providers.

3. benmccann ◴[02 Sep 25 13:40 UTC] No.45102981[source]▶
Only 3/40 Svelte maintainers work at Vercel and they mainly finance work on Svelte core. SvelteKit day-to-day is primarily maintained by folks outside Vercel
replies(1): >>45103105 #
4. gigatree ◴[02 Sep 25 13:49 UTC] No.45103105[source]▶
A little disingenuous to say “only 3/40” maintainers. Which 3? And how percentage of the total work hours invested per month do those 3 represent?
replies(1): >>45107186 #
5. benmccann ◴[02 Sep 25 18:34 UTC] No.45107186{3}[source]▶
The number 3, 4, and 5 contributors to SvelteKit in the past year work at Vercel: https://github.com/sveltejs/kit/graphs/contributors?from=8%2...

Rich and Simon are incredibly important, but they're in it for Svelte and the community more so than a paycheck from Vercel. Tee has been doing most of the maintenance on SvelteKit currently funded by community donations. And this isn't counting other infrastructure like vite-plugin-svelte or the Svelte CLI which are entirely maintained by volunteers. I don't think Vercel funds a majority of the work on Svelte even if it might be close to it.