Prusa-Firmware-Buddy VS jxl-oxide

>I don't believe QOI will ever have any sort of real-world practical use

Prusa (the 3d printer maker) seems to think otherwise: https://github.com/prusa3d/Prusa-Firmware-Buddy/releases/tag...

https://github.com/prusa3d/Prusa-Firmware-Buddy

Not open source? Odd, as I just read it's source code. Are you referring to licensing, ability to modify and compile yourself, or some else?

Did you use Prusa Link/Connect to upload the gcode? If so it looks similar to an issue reported by others where the gcode is getting corrupted. You can try putting files on the USB manually and printing from that as a temporary fix. May be helpful to take a look at this reddit thread or this github issue.

I made the issue here: https://github.com/prusa3d/Prusa-Firmware-Buddy/issues/3156

The github issue on it is worth reading to see just how poorly Prusa have handles this: https://github.com/prusa3d/Prusa-Firmware-Buddy/issues/677

Is 4.7 just the latest stable and I instead need this one?

Wow 100%. This actually pretty bad bug has been open for months with really no input from PRUSA other than “oh, wow that sucks. We’ll …uh… look into it.” https://github.com/prusa3d/Prusa-Firmware-Buddy/issues/2997

Pretty much every codec in every browser is written in an unsafe language, unfortunately. I don't see why JXL should be singled out. On the other hand, there is a JXL decoder in Rust called jxl-oxide [1] which works quite well, and has been confirmed by JPEG as conformant. Hopefully it will be adopted for decode-only usecases.

[1] https://github.com/tirr-c/jxl-oxide/pull/267

> It’s absolute insanity that we write codecs — pure functions — in an unsafe language that has a compiler that defaults to “anything goes” as an optimisation technique.

Rust and C++ are exactly the same in how they optimize, compilers for both assume that your code has zero UB. The difference is that Rust makes it much harder to accidentally have UB.

https://github.com/niutech/jxl.js a javascript polyfill taken from the main page https://jpegxl.info/

There are other decoders [0] written in a "safe language" (rust) listed as well. So no there are many "safe" implementations

[0] https://github.com/tirr-c/jxl-oxide

Found another JXL project in Rust called JXL Oxide. It's in its early stages so no need for a separate post yet imo. This other project is the Rust implementation of the JXL decoder.