j40

> I found it took me 3-4 months of absolutely nothing to not feel burnt out. That seems a universal experience. And to be more clear, absolutely nothing to think about, because even a sabbatical wouldn't save you if you think about post-sabbatical matters. I took a year of non-employment in 2022 after 7 1/2 years of working in the same big corp. My experience shows that it takes me 1 to 2 years until I start to feel burnt out and need something new to work on, and fortunately the company was able to provide such refresher on time (not necessarily at my request) but wasn't able to do this time. So I quit, and next 3--4 months were absolutely non-productive time for me. (I have a ton of side projects at any moment and I realized my burn-out from not being able to work on any of them.) But that followed by a very productive period without an

You can also force it by using extensions like `[[gnu::always_inline]]` or `__forceinline`. I've actually used this technique to generate an auto-vectorizable function whenever it's possible, without any code duplication [1]. [1] https://github.com/lifthrasiir/j40/blob/252e7987d36d50f617f2...

>The attempt to provide a second JPEG-XL implementation has stalled What do you mean by "the attempt"? There are at least three independent decoder implementations: jxl-oxide (Rust): https://github.com/tirr-c/jxl-oxide J40 (C): https://github.com/lifthrasiir/j40 jxlatte (Java): https://github.com/thebombzen/jxlatte None of them is feature complete, but it's because each of them is a hobby, single-person project. You're making it sound like some billion-dollar company tried to implement JPEG XL and failed, because it's too complex or something. However, it should be noted that those independent implementations, despite being hobby projects, helped to iron-out some minor issues in the standard. >Then AVIF got in, because AV1 was already in. AVIF uses its own container format that had to be implemented. Implementing AV1 does not give you AVI

There are a few alternative decoder implementations in progress. I believe J40 is the most complete one: https://github.com/lifthrasiir/j40

Chromium is an extremely large C++ code base and I don't think they would reject libjxl only for that reason. That said, as an author of the first significant reimplementation of JPEG XL format (J40), I think a Rust decoder would be a good addition to the format and has a long-term plan to make one [1]. [1] https://github.com/lifthrasiir/j40/issues/10

I've read the code and I know that it reimplements a substantial portion of Make. The point is however, this project doesn't work with a single Makefile either. Traditional projects would typically use configure plus (generated) Makefile, where configure is a shell script typically built from autoconf which is an abomination. In order to avoid autoconf some projects replace configure with other languages like JS. This project went further by merging that JS configure with Makefile. All of this hassle would be pointless unless you consider one important platform: Windows, where you don't natively have Make anyway. You may still argue that this project still requires GCC and thus there should be Make even in Windows. That's reasonable, but right now I have GCC and Clang but no Make in my Windows console. If you can remove a hard dependency

If you are interested in making a J40 binding in Rust, please also take a look at the future Rust version itself. I've made an initial issue [1] about this effort. [1] https://github.com/lifthrasiir/j40/issues/10

I believe the authors have made a very late draft available, as they have been unable to work around the processes that prevent them releasing the actual standard. The person who recently re-implemented it in C mentioned this. I thought it was in the Readme but maybe it was a comment here at HN: https://github.com/lifthrasiir/j40 Found it: https://news.ycombinator.com/item?id=32885536