7 ms·
For those who are unaware, this looks like a good article for the backstory. https://www.techspot.com/news/98355-google-deprecating-jpeg-xl-own-predatory-inter
by thyrox 3y ago
For those who are unaware, this looks like a good article for the backstory.
https://www.techspot.com/news/98355-google-deprecating-jpeg-xl-own-predatory-interests-fsf.html https://www.techspot.com/news/98355-google-deprecating-jpeg-...
- charcircuit 3y agoThis isn't a good article because of how biased it is against Google. It ignores that there is added cost to Google and their partners in supporting it and ignores the recommendation to use a WASM decoder.
- worrycue 3y agoOh please, Google’s parent company is worth 1.64 trillion USD. They can afford a few programmers to maintain a codec. Lack of popularity hasn’t stop them from supporting webp and AVIF.
- charcircuit 3y ago>They can afford a few programmers to maintain a codec. This is a bad argument because with that money they can also afford to do almost anything. They could also add any random file format to the browser, but that increases costs to support the web for more than just Google. Meanwhile adding a polyfill to support the format is performant without adding complexity to the web.
- jl6 3y agoIt’s also a bad argument because it confuses market cap with “money available to invest in developing products” (not that Google isn’t swimming in dumb money for other reasons).