libspng VS mozjpeg

It also works well on high-res, high-quality images with lots of single-color background and/or smooth gradients. But give it grainy, noisy, smaller-format images and it completely breaks down. We ended up sticking with PNG, which btw. Has fast open source implementations too [1][2]. [1] https://libspng.org/. - Source: Hacker News / over 1 year ago

That's why it's healthy to have competitors written in C. Like the library libspng, which has a simpler API than libpng. Or like samurai, a C reimplementation of the ninja build tool written in C++, or crun, a C implementation of a container launcher in contrast to the original written in Go. Source: over 1 year ago

It makes sense to treat it as an error but the ISO standard is too vague on this and the libpng developers never "fixed" this[1], it issues a warning but otherwise just masks off the high bits. Firefox has a workaround[2][3], Chrome doesn't. FWIW I do the same in my library[4], handling it as an error is problematic because it would mean the chunk gets discarded and then you can't even retrieve the values. [1]... - Source: Hacker News / over 2 years ago

It would be nice if the author would add mozjpeg[1] to the comparison. At certain sizes, it can produce smaller sizes than WebP, and because it is still a jpeg, it has a much better compatibility story, which the author alluded to. [1]https://github.com/mozilla/mozjpeg. - Source: Hacker News / 4 months ago

Image-shrinker is a simple, easy to use open source tool for shrinking images. Under the hood it uses pngquant, mozjpg, SVGO, and gifsicle. You can also install these tools individually if you need to compress some images. I often use pngquantafter exporting PNGs for web projects from Figma or similar tools. I literally run it like this:. - Source: dev.to / 7 months ago

> MozJPEG is a patch for libjpeg-turbo. Please send pull requests to libjpeg-turbo if the changes aren't specific to newly-added MozJPEG-only compression code. https://github.com/mozilla/mozjpeg#mozilla-jpeg-encoder-proj.... - Source: Hacker News / 9 months ago

FWIW, Mozilla has been maintaining their own fork for quite a while now[1] AFAIK most Linux Distros have been using libjpeg-turbo as a drop-in replacement for libjpeg, after some drama in ~2010 where libjpeg came under new management, decided to break ABI/API several times over and add incompatible, non-standard format extensions[2]. [1] https://github.com/mozilla/mozjpeg. - Source: Hacker News / 10 months ago

No. See https://github.com/mozilla/mozjpeg Also, there is a fairly big problem with JPG that the ‘quality’ setting is not calibrated. That is you might look at one image and think it looks fine (which is subjective, depends on what you want to use the image for…) with a quality of 60%, but then you compress a million images at that rate, delete the originals, then... - Source: Hacker News / about 1 year ago