5 ms·
This terse comment from the bug is an accurate summary of how projects work at Google, whose side effect was JPEG XL's removal: > The code has been removed fro
by lopkeny12ko 3y ago
This terse comment from the bug is an accurate summary of how projects work at Google, whose side effect was JPEG XL's removal:
> The code has been removed from Chromium (comment #281), I'm closing this bug for now. If leadership revisits the decision [1] it can be reopened.
There you have it--the people making decisions are out-of-touch, likely-non-technical managers, not engineers. Engineers are the ones writing the code and shipping features. Why not empower them to make these decisions?
- ed25519FUUU 3y agoNon-technical leadership is no longer a byword to me. I’ve sat through too many bikeshed meetings. Maybe JPEG-XL is more important to technical users than chromes actual users?
- jdiff 3y agoWithout a doubt. If you're lucky, they might know the difference between a JPEG and a PNG. This is a technical discussion at its core, you wouldn't expect Chrome's actual users to know about Flexbox or ES6, either. There's little you can't do without these, but things are transparently better with them anyway.
- pikelet 3y agoJust because they don't understand something or don't know about it doesn't mean it doesn't benefit them.