> the team at Google has agreed to apply their subject matter expertise to build a safe, performant, compact, and compatible JPEG-XL decoder in Rust<p>There's already a JPEG-XL decoder written in Rust: <a href="https://crates.io/crates/jxl-oxide" rel="nofollow">https://crates.io/crates/jxl-oxide</a><p>It would be nice to hear why it's not good enough.
Why just consider? Hell yes.<p>Anything that has remotely something to do with user-supplied data should be done in Rust, especially for such a high profile piece of software.
This is a great news for JPEG XL. Web standards need two independent implementations of every feature – this proves that the spec is actually possible to implement, and makes it possible to verify that the implementations are interoperable.
It makes uses in the wild much less likely to depend on bugs in a particular implementation, which makes it possible to upgrade or replace implementations without creating bug-compatibility problems.
> mozilla locked as too heated and limited conversation to collaborators.<p>I wonder which one was objected to - the implementation considered to be in Rust or that a rewrite might not actually make sense for the dying browser (2.75% share) at this stage?