Hacker News Reader

Comment by littlecranky67 | Hacker News Reader

Wouldn't say unnecesarry. Nextjs static export has features such as dynamic chunking, eager-loading of chunks when you hover over a link, routing etc. With a plugin you get image optimization (different image quality levels and dimensions based on viewport size) etc.

But yes, another static site blog generator would also work.

View on HN

> Wouldn't say unnecesarry. Nextjs static export has features such as dynamic chunking, eager-loading of chunks when you hover over a link, routing etc.

As someone who's ran a blog for 25 years it's surprising I never knew these things were necessary until now.

As someone who’s never ran a blog for the past 25 years it’s surprising I never knew a blog was necessary until now

As someone who's never ran for the past 25 years it's surprising I never knew.

All those features might be good in some contexts, but they're also literally the reason the author's blog couldn't get 100s on Lighthouse.

The picture element [1], [2] supports controlling which image is used via a media selector, allowing you to serve smaller images on smaller devices and on things like the viewport orientation.

[1] https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/...

[2] https://caniuse.com/picture

Great and all such, but it doesn't do the actual work of resizing your one highres image to all those breakpoints - which is part of the build process in NextJS.

My experience with Next.js is that because it mixes multiple paradigms, it makes using any single one of them more complicated and error prone.

Not just as the dev delivering the solution, but also library and package authors.

Ran into lots of issues around Next 12, Next 13 was very buggy, moved to Astro and never looked back.

Image optimization is the only thing in that list I might care about, and every CDN I’ve ever used provides it out of the box.

Reply on news.ycombinator.com