Hacker News Reader

Working with designers, I'm provided final images at spec and can only optimize them losslessly; compressing an image changes its appearance. The CLI commands in this article use lossy compression. The point stands, alternative image formats should be used whenever possible, but I need a lossless compression pipeline to generate WEBP, AVIF, etc.

View on HN

As someone who also works with designers, I understand at a deep level how you end up in this situation—but I also don't think it should be this way. Image compression should be primarily an engineering issue, and designers should be giving you lossless or effectively lossless[1] images to compress as you see fit.

The one thing I'd designers to be responsible for is image resolution, since this is intrinsically tied to website layout and affects white source photos can be used where.

[1] For example, a 100% quality jpeg is perfectly fine to work with.

> Image compression should be primarily an engineering issue

It affects how they look, so it's a design issue. I'd compress them all to 1% if it primarily an engineering issue.

Reply on news.ycombinator.com