@iamtakingiteasy @Inginsub @hideki Has it even been standardised yet?

@applejack @Inginsub @hideki Long time ago. The only obstacle is adoption by browsers, whose backing companies are suffering from NIH and peddling own failing bullshit.

@iamtakingiteasy @Inginsub @hideki >ISO/IEC 18181-1:2022

Nigga, that's this year. Since it's finally out though I should look at adding it to my software

JXL is cool but as of yet nothing supports it so it's not as useable as webp. I'll start adding it to my stuff though, at least as an optional feature

@applejack @Inginsub @hideki The spec itself was finalized long before that, most software started supporting it around 2010-2015.

@iamtakingiteasy @Inginsub @hideki Last year when I looked at it Gimp didn't even support it without an extension. Tested it now and works

It's getting there. Much better than I expected tbh

@iamtakingiteasy @Inginsub @hideki Wtf. Since when do you need to buy ISO standards. At least with png/webp it's formally open

@iamtakingiteasy @Inginsub @hideki Developed by google, heh

@iamtakingiteasy @Inginsub @hideki The reference implementation has a discord server, lmao

@applejack @Inginsub @hideki Since the beginning, I think. There is famously no public spec for C or C++ for example, only a bunch of drafts, and ISO reference costs something about $200-300. But where is indexing, there is a way.

@iamtakingiteasy @Inginsub @hideki There is an ISO C. Never new they were payed though, somehow

Early C "spec" was basically just K&R though

@applejack @Inginsub @hideki My memory is failing me. What I remember was actually a number of use-flags for gentoo/funtoo around that time under similar names, but those was either patchsets to libjpeg or jpeg-turbo, adding support. libjxl is indeed a reference for more formalized superset of same features and will only scheduled to complete standardization this year. Referenced spec is just the encoding details, file format is currently under way and there will also be docs for compliance and reference implementations.

@iamtakingiteasy @Inginsub @hideki Ye the docs rn don't look great. The API is documented but idk what it wants. I'll hold off for now

@iamtakingiteasy @hideki @Inginsub But what about JPEG2000?

@Drozdovsky @iamtakingiteasy @hideki the compression artifacts with JPEG2000 look worse than with the original JPEG, which is quite an achievement

@Inginsub @Drozdovsky @iamtakingiteasy @hideki And they had such high hopes for JPEG2000...

Look at the lower left, that's gnarly.

@Drozdovsky @Inginsub @hideki it was an attempt to introduce new modes of encoding, including lossless extensions, but never went far