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

Next.js 14

nextjs.org

Post reply on HN
Print view View original

71–80 of 157 posts

Re: Next.js 14

#71

Post by cyral »

orf wrote: post #63
cyral wrote: post #55

Earlier quoted context omitted.

The image component works fine when self-hosting, I use it on several production sites. What is it that doesn't work well without their cloud service? The default bundle size is also nowhere near 1MB. Next 13 and server components entire point is to reduce the bundle size by not shipping JS that is only ever called on the server.

How do I optimise and convert all my static image files to webp with a PNG fallback, then render them as a srcset so the client can pick the best image? I.e everything that’s done here[1] Oh no. You can’t. You need to set “images.unoptimized = true” and be happy about it if you’re not using a cloud image service. 1. https://docs.astro.build/en/guides/images/#properties

I'm not sure why this is your experience, but the site I am referencing does exactly that. The images are even being pulled from an external domain. They are not PNGs but I am not sure if that makes a difference (they are 100 quality .webp), they get optimized to a lower quality and have srcset, no vercel involved because I do not want a dependency on Vercel.

Re: Next.js 14

#72

Post by Palmik »

orf wrote: post #18

Fuck next.js. Honestly. Check out how it bundles and sends the entire react-dom library twice to every user on every page view https://github.com/vercel/next.js/issues/51508 . Fuck 1MB of JS to render a static HTML page. Fuck the image component, and not being able to optimise your image unless you use their cloud service for no reason at all. Fuck spending 3 hours working out why you’re not able to use relative imag…

Some of my favorite examples of NextJs suddenly breaking major things in minor releases:

Environment variables stopped working: https://github.com/vercel/next.js/issues/53367

The component stopped working: https://github.com/vercel/next.js/issues/53715

(Both of these were, afaik, exclusive to self-hosting, rather than running on Vercel)

Re: Next.js 14

#73

Post by garganzol »

leerob wrote: post #66
garganzol wrote: post #59

Next.js and Vercel are the same company. This means that the projects are susceptible to conflicts of interest. For example, pushing the server side forward while degrading the client story is the exact result one may get when such conflict is in effect. I'm sorry if this sounds too dark or unwarranted, but this playbook is too old to be dismissed.

Community Notes: Vercel did not acquire Gatsby.

Sorry, you are right - it was Netlify who acquired Gatsby. I have fixed the original message.

Re: Next.js 14

#74

Post by orf »

leerob wrote: post #61
cyral wrote: post #55

Earlier quoted context omitted.

The image component works fine when self-hosting, I use it on several production sites. What is it that doesn't work well without their cloud service? The default bundle size is also nowhere near 1MB. Next 13 and server components entire point is to reduce the bundle size by not shipping JS that is only ever called on the server.

next/image optimization works by default when self-hosting. You can optionally use basically any image service you want through a “loader file”. https://nextjs.org/docs/app/api-reference/components/image#l...

> Instead of optimizing images at build time, Next.js optimizes images on-demand as users request them.

Re: Next.js 14

#75

Post by ervine »

cphoover wrote: post #33

One weird issue I had with next 13 was radio button groups did not work. The suggested fix from a core next contributor and fb employee was to "Upgrade to a canary release"... I get that you are building all these new cool features, but that cannot put basic functionality and backwards compatibility at risk. Radio buttons have been around forever, I'd assume that they are being used by tons of websites all ove the pl…

Absolutely, this is the number one issue I have with next.js - they did a huge ecosystem-splitting update, but now recommend switching to the new paradigm for any issues with the old all while saying they are maintaining the old.

Re: Next.js 14

#76

Post by 10xDev »

Don't use tools that have turned into a product where they have people trying to lock you into whatever platform or any service they have. These aren't just engineers trying to help other engineers solve problems. These are marketeers trying to sell you hype.

Re: Next.js 14

#77

Post by willsmith72 »

shmde wrote: post #5

Wait wtf, I clearly remember 13 came out of beta 4-5 months back. At this rate Next.js will be on version 20 by the end of next year.

Yeah they have 14 versions in 7 years, 2/year. Angular has 15 in 7 years (counting ang 2+), so it's a close race but Angular is still coming out ahead.

Re: Next.js 14

#78

Post by cyral »

BoorishBears wrote: post #54
johnfn wrote: post #32

Earlier quoted context omitted.

> I want my JS on the frontend and not hot loaded from the server I'm fascinated by this. Literally, in every other HN thread in existence, you find stadiums of people shouting that they hate slow-loading SPA pages, and that all the work should have been done on the server, as God intended. Only on the release of Next.js 14 , of all things, do you find people saying that actually SPAs are great and SSR is a regressio…

You're falling for the trap Vercel laid by having RSC co-opt the concept of SSR. People are complaining about server components and the machinery to enable them: but those are actually unrelated to SSR. Client components are rendered on the server. - SSR was the sane middleground that worked since Next.js 1.0: You generated some content, and the frontend had all the Javascript and used that content to give a snappier…

What is wrong with that? I agree that Next 1.0-12.0 SSR was great. But, you were always shipping a ton of JS that may never be called for components that don't have any interaction. NextJS 13 now only ships what JS is needed.

Re: Next.js 14

#79

Post by jjkeddo199 »

As someone new who started with NextJS v13.4 on AWS, I am also disappointed that AWS/GCP/Others don't support all of Vercel's features. That being said, the commenters here are being unfair and unreasonable.

NextJS 13.4+ is nothing short of incredible. Are you telling me I can get a free, faster, opinionated, React implementation with 10's of finicky/unreliable/3rd-party Node_Module dependencies now seamlessly baked in for free? With a unified/simple build process too?

NextJS is nothing short of a lifesaver for small/indie web dev teams!

I do have my struggles + bloat + bugs using AWS instead of Vercel to host, no doubt, but that's out of my own cheapness/stubbornness. Vercel is not a charity, its a business -- I'm disappointed by commenters here basically complaining they don't "work for free".

Re: Next.js 14

#80

Post by ervine »

leerob wrote: post #58
jowday wrote: post #52

We've had an awful experience with Next. There are undocumented, broken things all over the place. Migrating to the App Router was a huge mistake. 'use client' didn't work as expected, and we had to install workarounds and try out different hacks to get access to the most pedestrian features we could expect from any other web framework. This is the broad consensus among everyone else I know using Next - they felt lik…

I’m sorry you haven’t had a good experience. And if you more specifics if anyone on the Next team replied to you in that way, please let me know. I’ll be the first to say the launch of the App Router could have been smoother. Definitely not the first time I’ve heard the feedback. I’m optimistic Next.js 14 is a step in the right direction based on this. What do you feel is undocumented? I’ll get that added.

https://github.com/vercel/next.js/issues/22319 https://github.com/vercel/next.js/discussions/46722

Let us take control when self-hosting, please!

Post reply on HN