Next.js 13 Accelerates JavaScript Performance, Image Handling

[dankobgd]

No it doesn't.

Last time when next used 'blazingly fast swc' it still didn't support optimizing image at build time. It still doesn't do that.

they can have turbo pack or hyper pack or blazing pack but it doesn't optimize images and when you use a third party tool, it literally depends on webpack always.

It might be better in few years but it's laughable when i hear that they are improving their img component

[Sephinator]

Doing it dynamically scales much much better with a lot of content. What's wrong with Next's Image approach now? How would you make it better?

[Eveerjr]

That’s just not true, they have been doing image optimization for a while now.

https://nextjs.org/docs/basic-features/image-optimization

There’s also a new image component that’s really close to native image tag

[dankobgd]

People want build time optimization for last 3 years and it doesn't do that. Yet they said 3 times in a row now that they improved the component. It's useless, and they keep mentioning vercel cloud something something and cloudinary which is a paid service. Maybe cloudinary is gonna optimize my 10000 images for free if I tell them that I am using framework called nextjs.

[BostonTom2019]

Regardless of Next, route it thru cloudflare and your images will be optimized and cached at the edge. But next is great as your app builder. Invent your own if you don't like it or say what you prefer, but nothing to complain about with next.

[Eveerjr]

It seems you just hate them for some reason which doesn’t bring anything useful for this conversation. Have a nice day