spoiler

made you look

  • 0 Posts
  • 19 Comments
Joined 8 months ago
cake
Cake day: July 27th, 2024

help-circle


  • They really want to promote their AVIF format, and supporting JXL would hinder that (Since JXL is a much nicer upgrade path from JPEG/PNG than AVIF is)

    Like you can transparently go from JPEG to JXL and back with no loss, which isn’t possible with AVIF. And PNG to JXL gives you a smaller file, while it’s usually the opposite with AVIF (Unless you get lucky, as lossless AVIF can be beaten by a BMP in a ZIP file). There’s also the issue of speed, AVIF is slow to encode compared to other formats (And while hardware decoding is possible, it’s also geared towards video, so the quality is often lacking, and can sometimes be slower than plain software encoding)






  • I think the biggest issue would be a lack of interfaces to the C side code, they’re slowly being fleshed out and each one enables more functionality for the Rust modules.

    e.g. the test Ext2 driver a MS dev wrote last year after enough of the filesystem interfaces got hooked up

    But even then, I don’t think the maintainers would accept one that replaces the existing C driver, that’d break non-Rust builds and architectures, and that’s a sure-fire way to get Linus on your case. Best you can hope for is one that complements a C driver, and even then I think you’d need a good reason to have two drivers for the same hardware.