@kajer webp has worse image quality than png unless compressed losslessly which most don't do (they use it to save space over a png)
also jpeg xl is better than both
with that said here's that image in a format i don't hate

@kajer webp is a fucking shit standard

@kajer "b-but JXL is less popular" everyone and their mum implemented JXL support, it's just Google that refuses to implement anything that's not theirs

@aviumcaravan @kajer

@esm @kajer that feels... outdated, considering the fact that i've opened JXL files in Firefox on both mobile and desktop.

also almost all of these browsers are just Chromium 😭

@aviumcaravan @kajer actually yeah, firefox technically does support JXL, and the page mentions this - but only in nightly builds, and only with a specific feature flag enabled (both of which are massive hurdles)

as of right now, you can not expect someone on, for example, a standard windows install to be able to easily open a jxl file without installing new software

@aviumcaravan @kajer (also i must point out that google was a contributor to the format's development, so it's absolutely theirs - which makes their stance on it weirder)

@esm @aviumcaravan @kajer i think it was something to do more with "the chrome team specifically hates jpegxl because they didn't have anything to do with it", but i may be wrong here

@Rairii @aviumcaravan @kajer @esm the official reasoning is i think that the reference decoder is written in a memory unsafe language which is not too unreasonable of a library where the immediate benefit is very low but the risk of it being exploitable is far higher

inconsistent standards tbh because from what i can tell the av1 decoder/encoder chrome is using is david and libaom1 respectively not rav1d/rav1e

@charlotte @aviumcaravan @kajer @Rairii @esm

I distrust Google as much as anyone, but googlers are actively working on the Rust JXL library, so it's not unconceivable JXL support will land eventually to Chrome.

https://github.com/libjxl/jxl-rs

@ttiurani @aviumcaravan @kajer @Rairii @esm yeah i am aware (although i forgot if they were working on it or were just open to adding it to chrome in the future)