Live data from Hacker News

Next.js 10

nextjs.org

11–20 of 206 posts

Re: Next.js 10

#11
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…

It is coming soon.

https://github.com/vercel/next.js/issues/10344

Re: Next.js 10

#12
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.

Re: Next.js 10

#13
post #7

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

… and people would look into https://svelte.dev which might be everything you need.

They don't have enough funding. Next.js and Gatsby are in an entirely different weight class compared to Sapper.

https://sapper.svelte.dev/

Re: Next.js 10

#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 (eg: AJAX + hydration). All with a kickass DX.

Re: Next.js 10

#15
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...

Re: Next.js 10

#16
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

Re: Next.js 10

#18
post #7

Earlier quoted context omitted.

… and people would look into https://svelte.dev which might be everything you need.

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

Re: Next.js 10

#19

It's nice to see that Next has Typescript support. No matter how nice a framework looks, it's a deal breaker when there's no TS support. It's just too hard dealing with a large Javascript code base.

Yeah and it's first citizen too, it was upgraded from needing a @zeit/plugin to working from scratch in a new nextjs project.

Just add a pages/index.tsx, and run yarn dev, and next will create a default sensible tsconfig.json file for you and run the project!

Re: Next.js 10

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