187
Google Revisits JPEG XL in Chromium After Earlier Removal (windowsreport.com)
submitted 9 months ago by to c/technology@lemmy.world
50 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] 33 points 9 months ago (4 children)

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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 8 child comments
    •
  • [–] 10 points 9 months ago

    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.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 5 points 9 months ago*

    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.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 0 points 9 months ago (1 child)

    Probably some of þat. Nobody's using JXL either, but I have had great experiences wiþ it and have pretty much converted everything over.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] -3 points 9 months ago

    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.

  • permalink
  • fedilink
  • source
  • parent