Live data from Hacker News

Next.js 10

nextjs.org

21–30 of 206 posts

Re: Next.js 10

#21
post #10

The big elephant in the room most of these frameworks are missing is partial hydration. Instead of hydrating the whole page, only the interactive parts are hydrated, sending the absolutely minimal JS needed to the client. AFAIK only Marko has this feature today. Since it's developed and used at Ebay they focused on the best SSR+hydration experience from the start. Imba v2 will also have patial hydration (confirmed by…

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.

Re: Next.js 10

#22
post #3

Highlights (live from keynote): - On-demand image optimization, lazy loading, via an Image component (responsive sizes, formats) - Internationalization support (routing via domain or subpath) - Next.js analytics. Automated performance testing and tracking https://nextjs.org/analytics - Next.js commerce. Starter kit for high-performance ecommerce https://nextjs.org/commerce Blog post: https://nextjs.org/blog/next-10 F…

Am I missing the part of the analytics docs / announcement where they mention how to send that information to anywhere other than Vercel? EDIT: described here in "web vitals" https://nextjs.org/docs/advanced-features/measuring-performa...

[deleted]

Re: Next.js 10

#23
post #10

The big elephant in the room most of these frameworks are missing is partial hydration. Instead of hydrating the whole page, only the interactive parts are hydrated, sending the absolutely minimal JS needed to the client. AFAIK only Marko has this feature today. Since it's developed and used at Ebay they focused on the best SSR+hydration experience from the start. Imba v2 will also have patial hydration (confirmed by…

The React team is working on some experiments that’s not quite what you’re describing but achieves the goal of sending way less code to the client. I can’t wait until tools like that are more standard.

There is light at the end of the SPA tunnel :)

Re: Next.js 10

#24
Does Next.js do pre-rendering, i.e. if I have a store with 500 products, will it pre-render the HTML (photos, etc.) for all 500 products and serve it as a static request? Or will it assemble the template on the server, send it down to the client and then do some amount of interactivity hydration later on during the page load?

What if my store has multicurrency / multilingual versions of all these 500 pages - will it pre-render all of these combinations?

I haven't used a JS framework with server-side rendering in a while - but from what I remember it seemed to add a terribly high TTFB to the overall page load, which negatively impacted SEO. As a result we abandoned SSR based frameworks completely and just went with minimal JS on the client and pre-rendered all the pages on the server as HTMLs which loaded pretty much instantly.

Most of the time when I see the "new hotness" being advertised, there don't really seem to be any specifics that tackle advanced use-cases so it's difficult to accurately assess whether the technology is worth serious consideration

Re: Next.js 10

#25
I can't believe NextJS still doesn't have named routes, resorting to hacks like next-routes or next-named-routes to have a semblance of sanity managing links throughout larger apps.

Also, doing things like /@[username] is still a huge hack, unsupported.

Re: Next.js 10

#26
post #24

Does Next.js do pre-rendering, i.e. if I have a store with 500 products, will it pre-render the HTML (photos, etc.) for all 500 products and serve it as a static request? Or will it assemble the template on the server, send it down to the client and then do some amount of interactivity hydration later on during the page load? What if my store has multicurrency / multilingual versions of all these 500 pages - will it…

> if I have a store with 500 products, will it pre-render the HTML (photos, etc.) for all 500 products and serve it as a static request?

You can set it up to retrieve all 500 products and render the html on the server.

> What if my store has multicurrency / multilingual versions of all these 500 pages - will it pre-render all of these combinations?

The server is making all the requests that would have been made on the frontend. So if the server knew the locale of the user it could presumably load the correct currency and language.

Re: Next.js 10

#27
post #24

Does Next.js do pre-rendering, i.e. if I have a store with 500 products, will it pre-render the HTML (photos, etc.) for all 500 products and serve it as a static request? Or will it assemble the template on the server, send it down to the client and then do some amount of interactivity hydration later on during the page load? What if my store has multicurrency / multilingual versions of all these 500 pages - will it…

Next.js can do both pre-rendering (static output) and dynamic server-side rendering. I can't speak to your questions about internationalization though.

Re: Next.js 10

#28
post #24

Does Next.js do pre-rendering, i.e. if I have a store with 500 products, will it pre-render the HTML (photos, etc.) for all 500 products and serve it as a static request? Or will it assemble the template on the server, send it down to the client and then do some amount of interactivity hydration later on during the page load? What if my store has multicurrency / multilingual versions of all these 500 pages - will it…

yes, next will prerender everything. you should give it a try.

Re: Next.js 10

#29
post #14

Prediction: Google buys Vercel, kills Angular, steps further into e-commerce

Could be. Angular growth has stalled for the past year or so. Polymer is pretty much dead. OTOH hand why would Google invest in a React-based solution? Google could start from scratch an create the next best thing if they wanted to. To me it's pretty clear the future is a compiler based approach like Svelte, with support for SSR, partial hydration, static generation, and dynamically loading smaller parts of a page (e…

They could buy Vercel & Next with the intention of rolling their own React replacement to swap in later.

Re: Next.js 10

#30
post #18

Earlier quoted context omitted.

They don't have enough funding. Next.js and Gatsby are in an entirely different weight class compared to Sapper. https://sapper.svelte.dev/

And... Sapper is dead btw. Rich said it recently in a video. The Svelte team is working on the next big thing combining Svelte with Snowpack. The project is called SvelteKit. https://www.youtube.com/watch?v=qSfdtmcZ4d0

I think retiring Sapper was the right decision. I have a feeling Rollup will meet a similar end too.

They both seemed like fine pieces of software. They just don't seem offer separate much their counterparts nowadays that warrants continued feature development.

Post reply on HN