4 ms·
Is there a reason that browsers don't jump on the bandwagon and implement codecs for all reasonably-stable image codecs (save this one, which seems to be patent
by sneak 7y ago
Is there a reason that browsers don't jump on the bandwagon and implement codecs for all reasonably-stable image codecs (save this one, which seems to be patent encumbered)?
i.e.: why doesn't Chrome support AVIF? Is it because it competes with their own invented-here WebP?
It seems like adding new image codecs for given content types would be pretty trivial if the libraries are available and stable and license compatible; why be conservative and not just support the newish ones to help the best ones gain traction?
It seems like browser vendors are just dragging their feet.
- noisem4ker 7y agoSecurity liabilities, most likely. Buggy decoder libraries widen the surface for exploits. And no software is bug free, nor first party vetting is free, nor sandboxes can be blindly trusted to do their job. Better not to take any unnecessary risk, especially since browsers are already complicated enough.
- theandrewbailey 7y ago1. Security 2. Bloat 3. You can't really stop supporting media formats. Once you put anything into a browser, you can't take it out. The best that can be done is depreciate it forever.
- timw4mail 7y agoBecause browsers have an enormous API/file support surface as is, and each new image format can be a significant amount of code to support essentially forever. Webp now is supported by pretty much every browser, but a lot of image viewers don't support the format yet. There has to be a certain amount of momentum to justify supporting a new image format.