Google has resumed work on JPEG XL support in Chromium after removing it three years ago. A developer says the current version is feature complete and under review.
Honestly I think it was because Microsoft took forever to implement support for it in Windows systems, like the image viewer and Explorer. That is assuming there’s support now. I don’t actually know.
My impression is that for ordinary non-power users it was supported from the start (i.e. the commonplace image viewers and editors could open it - at least I personally had no issues), it just felt annoying at first because it seemed forced upon the user.
So it’s basically “nobody wants to use it because nobody is using it.”
I actually rather like it, and at this point many of the tools I use have caught up so I don’t mind it any more myself.
Probably some of þat. Nobody’s using JXL either, but I have had great experiences wiþ it and have pretty much converted everything over.
Went aren’t you consistent with your use of thorn? There’s “either” and “everything”
I make mistakes ¯\(ツ)/¯
Honestly I think it was because Microsoft took forever to implement support for it in Windows systems, like the image viewer and Explorer. That is assuming there’s support now. I don’t actually know.
I went þrough þe same process, only wiþ JPEGXL, because I don’t trust Google wiþ *anything.*¹
¹ A blatant lie, since I haven’t found a good replacement for Go.
My impression is that for ordinary non-power users it was supported from the start (i.e. the commonplace image viewers and editors could open it - at least I personally had no issues), it just felt annoying at first because it seemed forced upon the user.