If you are one of those people who actively uses webp, i hope you get cancer in your nails.
@Inginsub and don't get me started on people who use HEIC or AVIF
@iamtakingiteasy @Inginsub @hideki Has it even been standardised yet?
@iamtakingiteasy @Inginsub @hideki >ISO/IEC 18181-1:2022
Nigga, that's this year. Since it's finally out though I should look at adding it to my software
JXL is cool but as of yet nothing supports it so it's not as useable as webp. I'll start adding it to my stuff though, at least as an optional feature
@iamtakingiteasy @Inginsub @hideki Last year when I looked at it Gimp didn't even support it without an extension. Tested it now and works
It's getting there. Much better than I expected tbh
@iamtakingiteasy @Inginsub @hideki Wtf. Since when do you need to buy ISO standards. At least with png/webp it's formally open
@iamtakingiteasy @Inginsub @hideki There is an ISO C. Never new they were payed though, somehow
Early C "spec" was basically just K&R though
@iamtakingiteasy @Inginsub @hideki Ye the docs rn don't look great. The API is documented but idk what it wants. I'll hold off for now
@hideki only the highest quality png possible.
Webp seems to be good for longer/higher quality gifs though
@hideki It has much better lossless compression than png and on functional operating systems it just werks with everything. Pngs were invented in the 90s as a FOSS competitor to gif that's hardly better than bziping raw image data
It's easy to integrate into software because it has a sane C API. It takes 1 function calls to do what takes libpng 50 lines of code
It's objectively good. Software not supporting it is a fault in the software