5 ms·
> It's a C++ library that Google needs to secure and maintain security patches forever. Compile it to wasm and run it in a sandbox? Or throw some rust groupies
by josefx 3y ago
> It's a C++ library that Google needs to secure and maintain security patches forever.
Compile it to wasm and run it in a sandbox? Or throw some rust groupies at it?
> Once released, it's pretty much impossible to rollback support for media formats on the web.
We must live in a time where flash still dominates short web animations, streaming providers use silver light and every enterprise user is stuck waiting for the companies 5GB Java applet to load right when IE6 suddenly pops up to kill everything with an ActiveX based Windows update that adds more video codecs instead of removing them from the system. The list goes on forever. Browsers are not above killing features and breaking things for security reasons or if they just feel like it.
- magicalist 3y agoMaintaining your own rust fork of a codec or forcing the web through another painful breaking change drawn out over years seem like fantastic arguments to wait until the ecosystem is visibly moving to jpegxl before committing to it, actually.
- spider-mario 3y agoIt wouldn’t be a fork, it would be another implementation. There are already a few.