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

Next.js 10

nextjs.org

Post reply on HN
Print view View original

101–110 of 206 posts

Re: Next.js 10

#101

Post by rory »

drdaeman wrote: post #80
rory wrote: post #36

Earlier quoted context omitted.

It _can_ prerender all of those combinations. Here is a directory I made with 1000+ pages, prerendered and hosted for free on netlify: https://www.givepuppylove.com/organizations/ . I've found that single digit thousands is about the maximum you can currently have and keep build times reasonable. If you want to recognize the user's location and display the appropriate currency or language, you would probably want to…

What happens if there are millions of pages? Wish Next.js would have a "scalability issues and solutions" documentation...

Like acoard said below, I think the recommendation there would be to use their hybrid cache / dynamic rendering option. You do lose a lot of the cool benefits of being fully static in that case though. In general, yes that kind of documentation would be very helpful.

Re: Next.js 10

#102

Post by pbowyer »

robocat wrote: post #91
pbowyer wrote: post #40

> Nowadays users browse the web using their phones, tablets, and laptops, yet images are still as a one size fits all. For example: sites load a 2000 by 2000 pixel image, but phones are only displaying it as 100 by 100 pixels. That's what srcset & were invented for. > Furthermore, 30% of images on web pages are outside of the initial viewport, meaning the browser loads images that a user does not see until they scrol…

> How can smart preloading work when the image size isn't known until the JS component runs? From the article: - Image dimensions are enforced, allowing browsers to immediately render the space needed for the image instead of having it jump in when loaded, preventing layout shift. - While width and height on the HTML element can cause issues with responsive layouts, this is not the case when using next/image. When us…

Image dimensions is great, but isn't the same as preloading, which is done via a HTTP header or a

See https://web.dev/preload-critical-assets/ for more details.

Re: Next.js 10

#103

Post by rory »

acoard wrote: post #90
rory wrote: post #42

Earlier quoted context omitted.

As far as count of pages Vercel has a limit of 16000 and Netlify technically has no limit (AFAIK), although the build times will cost you eventually. You can work around this limit in a lot of cases while keeping things prerendered by putting dynamic information in querystrings.

You're totally right. Apparently this on the Nextjs team's radar though: >Up next, we will be working on a supplemental RFC to address two additional incremental static generation capabilities: > - Re-generating and invalidating multiple pages at once (like your blog index and a certain blog post) > - Re-generating by listening to events (like CMS webhooks), ahead of user traffic Source: https://nextjs.org/blog/next-…

Right, actually building all those pages at once necessarily takes time. But on Netlify, most of my build time isn't actually used doing `next build`, it's the un-logged-to-user file transfer to their server / CDN cache invalidation / whatever hosting magic they do after the static files are built.

So at least in my case, NextJS would have to create a way to not rebuild files that haven't changed, and then the hosting/CDN provider would also need to be able to see which files those are and respond accordingly. This all seems very doable eventually though.

Re: Next.js 10

#104

Post by dnissley »

pier25 wrote: post #21
tshaddox wrote: post #16

Earlier quoted context omitted.

The React team is or was reportedly working on "progressive hydration" which sounds like what you're talking about. This tweet from React core team member Dan Abramov in December 2018: https://twitter.com/dan_abramov/status/1079352276433715200

They've been talking about it for years alongside with SSR streaming. Nothing concrete so far.

Is this not SSR streaming? https://reactjs.org/docs/react-dom-server.html#rendertonodes...

Re: Next.js 10

#105

Post by [deleted] »

x87678r wrote: post #35

I tried nextjs because I thought it would be a good way to learn React but I found it really confusing. Is it really better to master React first then try nextjs?

[deleted]

Re: Next.js 10

#106

Post by citruspi »

mindrun wrote: post #100
bamazizi wrote: post #71

I understand this is a Vercel framework and probably a great distribution channel for new business and increasing overall revenue. But, I'm a bit disappointed the "next" version is more about Vercel's own internal business agenda. Promoted as amazing "DX" is not really true. It had a better DX compared to the other tools, that's why it grew so popular, but not seeing anything real DX related in version "10". Other to…

Whenever the Next.js + Vercel combo gains a new feature, Vercel ensures that it's available in standalone Next.js too – even when deployed to other providers. That's true for all the features mentioned in the Next.js 10 blog post: Image optimization, Internationalization, but also Analytics. Since you mentioned the latter: Did you notice that we wrote a detailed documentation page about how to report those metrics to…

> Did you notice that we wrote a detailed documentation page about how to report those metrics to any service of your choice?

Perhaps you should link that on the Analytics[0] page instead of directing users to contact the sales team for more information on non-Vercel deployments.

[0] https://nextjs.org/analytics

Re: Next.js 10

#107

Post by sandGorgon »

Nextjs has the dejavu vibe of docker.

It is a brilliant framework dragged slowly and inexorably into "platform lock-in".

Nextjs has defocused on SSR (which was the original selling point of a server side Reactjs). And all the other cool features only run on Vercel.

It is getting next to impossible to deploy Nextjs (with all its features) on GAE for example...or heroku.

There are other alternatives to Nextjs that are emerging with true developer fit - think databases,etc. Svelte, etc are pretty cool

Re: Next.js 10

#108

Post by dntrkv »

deft wrote: post #33
airstrike wrote: post #20

As someone who only really built websites using jQuery / custom vanilla js and good ole CSS2, this stuff feels completely alien to me

Same. I mean I understand how it works but I ask myself what's the point every time. I've looked into react and I hate how it works and I hate how every 2 months people are begging for some new optimization because its slow and sucks. Then version 5000 is released and fixes that slowdown, but every react site I've ever used is still buggy and slow as hell.

> hate how it works

> its slow and sucks

> every react site I've ever used is still buggy and slow as hell

Next time try to come up with some rational, objective criticism instead of just hurling insults at the most popular frontend framework.

There is a reason people use it, and believe it or not, it's not due to hype.

Re: Next.js 10

#109

Post by yawnxyz »

bamazizi wrote: post #71

I understand this is a Vercel framework and probably a great distribution channel for new business and increasing overall revenue. But, I'm a bit disappointed the "next" version is more about Vercel's own internal business agenda. Promoted as amazing "DX" is not really true. It had a better DX compared to the other tools, that's why it grew so popular, but not seeing anything real DX related in version "10". Other to…

I'm rewriting a bunch of my Vue components into Svelte, and turning my Nuxt (which were previously React/Next) projects into Sapper, and it's a crazy easy process. My Svelte codebase is tiny compared to my Vue codebase.

I'm slightly "worried" about Sapper not being at v1.0 yet but... it's been working great for my MVPs

Re: Next.js 10

#110

Post by fasteo »

erokar wrote: post #87
bamazizi wrote: post #71

I understand this is a Vercel framework and probably a great distribution channel for new business and increasing overall revenue. But, I'm a bit disappointed the "next" version is more about Vercel's own internal business agenda. Promoted as amazing "DX" is not really true. It had a better DX compared to the other tools, that's why it grew so popular, but not seeing anything real DX related in version "10". Other to…

I feel the same way. We've switched from React to Svelte at work. Going back to React would be a step backwards for us, so much feels needlessly overengineered with awkward APIs. React was a great improvement on Angular, but luckily things are still moving forward.

Which UI component library, if any, do you use with Svelte ?
Post reply on HN