3 ms·

Then why is it C/C++? To be allowed into the browser, a new codec ought to be implemented in a memory-safe language.

• lifthrasiir 3y ago
  Because browser vendors have already invested too much into the existing C/C++ code base. They can thus accept new code with the same degree of coding standard.
  • acdha 3y ago
    Those same vendors are using Rust and Swift now which have comparable performance and solid interoperability. It seems like time for a policy saying new internet-facing code be implemented in a safe language.
    • saagarjha 3y ago
      Browser vendors are ahead of you on this. They just need time to put it into practice.
      • acdha 3y ago
        Yes - I know both Mozilla and Chrome are doing this. The main thing I was thinking is that it’d be a lot more supportable if the response was, say, “we’ll add JPEG-XL only in Rust”.