7 ms·
"Yes, re-opening.". > Given these positive signals, we would welcome contributions to integrate a performant and memory-safe JPEG XL decoder in Chromium. In or
by markdog12 10mo ago
"Yes, re-opening.".
> Given these positive signals, we would welcome contributions to integrate a performant and memory-safe JPEG XL decoder in Chromium. In order to enable it by default in Chromium we would need a commitment to long-term maintenance. With those and our usual launch criteria met, we would ship it in Chrome.
https://groups.google.com/a/chromium.org/g/blink-dev/c/WjCKcBw219k/m/NmOyvMCCBAAJ https://groups.google.com/a/chromium.org/g/blink-dev/c/WjCKc...
- bigbuppo 10mo agoLOL. Google, the "yeah that thing we bought six months ago, we're killing it off 30 days for 4 weeks ago" company demanding "long-term" anything.
- lonjil 10mo agolong term support is actually being provided by google... just a different team in a different country :D most jxl devs are at google research in zurich, and already pledged to handle long tetm support
- malfist 10mo agoJust like google pledges long term support for everything until the next new and shiny comes along.
- rjh29 10mo agoThat conversation doesn't apply to their core products: Search, Mail, Maps, Chrome, Android. Their commitment to maintaining these services over decades has been amazing. It's everything else that sucks.
- professor_v 10mo agoMail is dropping features left and right, like gmailify. I'm pretty sure they're trying to limit the maintenance costs as much as possible.
- PaulHoule 10mo agoI could almost imagine the normal search going away to be replaced by a chatbot.
- concinds 10mo agoContext: Mozilla has had the same stance and many devs (including Googlers) are already working on a Rust decoder which has made good progress.