this post was submitted on 06 Aug 2024
340 points (92.3% liked)
Technology
58138 readers
4192 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
https://xkcd.com/927/
Adding more decoders means more overheads in code size, projects dependencies, maintanance, developer bandwidth and higher potential for security vulnerabilities.
The alternative is to never have anything better, which is not realistic
Yes, it means more code, but that's an inevitability. We already have lots of legacy stuff, like, say, floppy disk drivers
A balance has to be struck. The alternative isn't not getting anything better, it's being sure the benefits are worth the costs. The comment was "Why is [adding another decoder] a negative?" There is a cost to it, and while most people don't think about this stuff, someone does.
The floppy code was destined to be removed from Linux because no one wanted to maintain it and it had such a small user base. Fortunately I think some people stepped up to look after it but that could have made preserving old software significantly harder.
If image formats get abandoned, browsers are going to face hard decisions as to whether to drop support. There has to be some push-back to over-proliferation of formats or we could be in a worse position than now, where there are only two or three viable browser alternatives that can keep up with the churn of web technologies.
I mean, the comic is even in the OP. The whole point is that AVIF is already out there, like it or not. I'm not happy about Google setting the standards but that has to be supported. Does JPEGXL cross the line where it's really worth adding in addition to AVIF? It's easy to yes when you're not the one supporting it.