Are we Wayland yet? Are we JPEGXL yet? Are we Rust yet?

I’ve gathered a meta-tracker for the adoption state of futuristic technologies.

  • pivot_root@lemmy.world
    link
    fedilink
    arrow-up
    50
    arrow-down
    2
    ·
    6 months ago

    A reminder: Google added support for and then subsequently dropped JPEGXL support in Chrome. Fuck Google.

        • bl4kers@lemmy.ml
          link
          fedilink
          English
          arrow-up
          7
          ·
          6 months ago

          I played high-end games I couldn’t otherwise play, often at a discount, and then they refunded me at the end anyway. Pretty sweet deal

        • kelvie@lemmy.ca
          link
          fedilink
          arrow-up
          2
          ·
          6 months ago

          Well you have to state why it wasn’t good. It was incredibly region-dependent, but if you live near one of their endpoints the latency wasn’t noticeable and the quality was great, as it was for me.

          In the end I got to play a bunch of games for free, and have an extra controller I still use, so there’s that. They made us whole, at least, after they shut down (I even imported my into the breach save game into Steam with Google takeout after)

      • Vincent@feddit.nl
        link
        fedilink
        arrow-up
        8
        ·
        6 months ago

        What is it with this obsession with JPEG-XL? I keep seeing it mentioned on lots of threads, but as a user, the benefits seem marginal? Like: would be nice, but I’d expect more significant benefits from something that’s brought up this often - so which benefits am I missing?

        • EveryMuffinIsNowEncrypted@lemmy.blahaj.zone
          link
          fedilink
          English
          arrow-up
          5
          ·
          edit-2
          6 months ago

          Honestly? I agree with you that the benefits seem kind of marginal. But I still think it’s a fascinating thing. :)


          Edit:

          On doing some reading about it and trying it out for myself, the file size reductions are hardly marginal. It’s actually quite impressive. Still, it seems for most people, including myself, that jpeg for lossy & png for lossless is more than adequate, especially with how cheap storage is nowadays.

          (And, frankly, I appreciate seeing at a glance if an image is lossy or lossless, but I imagine that’s a priority most people don’t have. Lol.)

        • EveryMuffinIsNowEncrypted@lemmy.blahaj.zone
          link
          fedilink
          English
          arrow-up
          6
          ·
          6 months ago

          Because it’s yet another example of Google’s near-monopoly over the Web’s architecture. It’s not healthy for good web development. It’s like the 90s and Microsoft all over again.

          I mean, fuck, we’re already getting websites that’ve been “optimized” for Chromium-based browsers—in other words, semi-broken for non-Chromium browsers.

            • EveryMuffinIsNowEncrypted@lemmy.blahaj.zone
              link
              fedilink
              English
              arrow-up
              4
              ·
              edit-2
              6 months ago

              I said a near-monopoly. Also, even if it’s foss, by creating the format, they established the baseline parameters of that format.

              That gives them a significant degree of control.

               


              Edit: I also hate it because so many of the programs I use don’t support it, so I constantly have to copy > paste into image editor program > Save as PNG.

              Though admittedly this is mostly an adoption thing. Still, it’s a major problem.