-
Notifications
You must be signed in to change notification settings - Fork 229
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"FLIF is dead, and JPEG XL has killed him" is this true? #549
Comments
I am curious of the same thing. FLIF was something I was extremely interested in from day 1. I watched the grass grow and turn brown on the Chromium feature request with many arguing web developers would not be interested. Hogwash! Absolutely not true! Now i’m checking in again finding many of these updates that the original dev has moved on and it’s sad to see. I think FLIF on mobile browsers would have been stupendous. It still can be. |
Well, I don't know that I'd quite say that the original developer "moved on", per se. As I understand it, Jon Sneyers created FLIF, then FUIF as a successor. Now FUIF + Google's PIK were used as the starting point for JPEG XL. I'm not sure how brunsli fits in, but I'm assuming it as the repository states "the transport layer" - not the whole thing. So I'm not quite sure that it is a replacement exactly? Can anyone comment a bit more about how brunsli fits into the big picture? |
@wingman-jr-addon Brunsli is one of the repo that converts JPEG into JPEG-XL I think. https://google.github.io/brunsli/ |
Ah, I found a bit more on how the two are related. |
Okay so the AVIF guys are planning to revamp WebP into a version 2 to compete with JXL... |
Brunsli was originally part of JPEG XL (Annex M indeed), but it was removed to keep the spec simpler, since the regular VarDCT mode (using only 8x8 blocks so not really "var") offered similar compression with a better decode speed. JPEG XL as it was finalized in January 2021 has only two modes:
|
Since https://github.com/google/brunsli has come up as a good alternative to FLIF, FUIF and PIK,
Is it possible to do a final comparison between the compressed sizes and compression artifacts of JPEG vs previously tested image foarmats, FLIF, FUIF, PIK, HEIF and AVIF vs JPEG-XL so that we can see what the future look like.
The title is a variant from Nietzsche's quote about the futility of faith.
The text was updated successfully, but these errors were encountered: