2 ms·
> Web browser vendors have been reluctant to implement it because of increases attack surface, and of course web sites will not use it without browser support.
by captainmuon 11y ago
> Web browser vendors have been reluctant to implement it because of increases attack surface, and of course web sites will not use it without browser support.
I believe codecs should actually be part of the OS. There should be one good, well-tested implementation per OS that browsers and other apps just link to. It might actually be possible to sandbox the codec components for increased security. Ideally, a web browser would just be a HTML+stuff parser, a layout engine, and a bit of gui, and shell out to the OS for everything else. Unfortunately, it seems the monolithic kitchen sink model has won.
- vetinari 11y agoThe monolithic kitchen sink has won, because the OS bundled libraries have different APIs (not only among different OSes, but also among different versions - and OS vendors are interested in pushing the latest), so app vendors just said to themselves "screw it" and bundled library (like jpeglib or libpng) that has same API on all systems and versioning is under their control. That's the short version ;).