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

71–80 of 206 posts

Re: Next.js 10

#71

Post by bamazizi »

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 tools are starting to do things a bit better.

Analytics, great idea, is a huge disappointment. It's just a Vercel thing and not NextJS, not to mention a "pro/enterprise" paid feature, not cheap either.

A few days ago I saw the YT videos of "future of Svelte" and that video was really about "DX" with no non-sense no BS that just focused on the real next evolution on web/app dev. That DX really resonated with me.

My opinion, I'm not sold on NextJS 10, the "commercial" move kind of turned me off and scares me of platform lock-in, but I'm getting more and more interested into Svelte (v4?) and I'm seriously looking to switch to it from NextJS.

Note: "DX" stands for "Developer eXperience", meaning how joyful, easy it is to get started with the tool and feeling productive.

Re: Next.js 10

#72

Post by preommr »

HendrikR wrote: post #7
aloukissas wrote: post #6

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.

Or even better, Vue.js

I am not sure I buy into all the svelte hype, and even if claims about it's speed/build size are true - the difference isn't enough to outweigh the enormous advantage vue has in terms of a more mature ecosystem/tooling.

Re: Next.js 10

#73

Post by pier25 »

ampdepolymerase wrote: post #11
pier25 wrote: 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

It's not. That issue is closed and the last comment says:

> Overall it’s currently not possible to do this besides following what’s described in the article. Definitely something we plan on tackling eventually!

Re: Next.js 10

#74

Post by jaredklewis »

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…

> That's what srcset & were invented for.

next/image makes use of srcset.

> This has been done many times before. For images outside the viewport it's great; for images which are in the viewport, the browser isn't able to discover the image until the JS has loaded and decided which image size to fetch. In my experience this slows down the overall rendering of the page. >I see the Google Chrome team was involved in creating this component so I'd like to know what's different this time, because they have the data.

No knowledge of what Google contributed to this, but my experience of running Google PageSpeed Insights on many sites is that this sort of optimization does improve the metrics Google measures.

Also, while I agree in part with most of your points, I still think we should give credit to nextjs for making this easy.

Sure, maybe you don't need a library to use srcset. If you are going to run our own custom build processes (or server endpoints) that generate images in a range of appropriate sizes and write the corresponding front-end code, good for you. Next.js has done nothing to stop any of this.

But many (most?) websites don't bother with any of that and just load one giant image for everyone. If there is a tool that makes using optimized images as easy loading one giant image for everyone, I think that's great.

Re: Next.js 10

#75

Post by hitekker »

rich_harris wrote: post #68
hitekker wrote: post #30

Earlier quoted context omitted.

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.

Rollup isn't going anywhere! When you poke behind the scenes of newer build tools, like Snowpack and Vite and the custom compiler that powers Remix Run, you'll find Rollup doing a lot of the heavy lifting. And it's the preferred choice of most libraries. There's a reason for that :)

Thanks for the correction, Rich.

I just watched your presentation at Svelte Summit and I'm looking forward to how Svelte progresses.

Re: Next.js 10

#76

Post by fuzzy2 »

TheMagicHorsey wrote: post #62

Am I the only developer that feels that React ... and perhaps the whole web paradigm ... is about the worst way to think about and develop client GUIs? After using Google's new Flutter framework (which is built to develop cross platform apps: iOS, Android, Web, embedded) I felt like I had my eyes open. The structure seems so much more logical and easy to navigate. The Web (and React) paradigm of putting some code in…

React doesn't have HTML templates though…? You can also have CSS-in-JS if you really want.

Re: Next.js 10

#78

Post by jayflux »

o_____________o wrote: post #50
truesy wrote: post #45

I have mixed emotions on this framework. If you're doing a simple project, Next is the best around. Also great for marketing pages, etc. But if you have a more sophisticated app, with an API, page routes that need to toggle based on cookies, etc, then you have to integrate something like Express. I've done this several times with Next, and it just doesn't pay off. I've also tried to use it at work, but it changes rap…

Why do you have to integrate with Express? Genuinely asking – that wasn't my impression.

I think he means if you want to offer React server side you will need some-sort of web framework to serve it. Usually that's Express or Fastify or something like that.

Re: Next.js 10

#79

Post by pier25 »

eitland wrote: post #48
pier25 wrote: post #18

Earlier quoted context omitted.

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

Maybe this can save someone some confusion: When I searched the first result for SvelteKit seems to be another project that is dead.

Should be called SveltePack IMO :)

Re: Next.js 10

#80

Post by drdaeman »

rory wrote: post #36
fareesh wrote: 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…

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

Post reply on HN