jxl-oxide | jxl-rs | |
---|---|---|
6 | 1 | |
207 | 27 | |
- | - | |
9.4 | 10.0 | |
3 days ago | over 1 year ago | |
Rust | Rust | |
Apache License 2.0 | BSD 3-clause "New" or "Revised" License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
jxl-oxide
Posts with mentions or reviews of jxl-oxide.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2024-03-01.
-
JPEG XL and the Pareto Front
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.
-
Still no love for JPEG XL: Browser maker love-in snubs next-gen image format
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
- jxl-oxide: A pure Rust implementation of the JPEG XL decoder
-
jxl-winthumb: A JPEG XL (*.jxl) thumbnail handler for Windows File Explorer in Rust
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.
jxl-rs
Posts with mentions or reviews of jxl-rs.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2024-02-04.
What are some alternatives?
When comparing jxl-oxide and jxl-rs you can also consider the following projects:
jxl-winthumb - A JPEG XL (*.jxl) thumbnail handler for Windows File Explorer.
thorium-libjxl - libjxl for Chromium - restores JPEG-XL functionality to Thorium/Chromium post M109