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.

    • Vincent@feddit.nl
      link
      fedilink
      arrow-up
      0
      ·
      5 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
        0
        ·
        edit-2
        5 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.)

        • Vincent@feddit.nl
          link
          fedilink
          arrow-up
          0
          ·
          5 months ago

          Yeah that’s what I mean - it’s not that the file size reduction is minimal, but that the benefits of that are fine, but not earth-shattering.

      • EveryMuffinIsNowEncrypted@lemmy.blahaj.zone
        link
        fedilink
        English
        arrow-up
        0
        ·
        5 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
            0
            ·
            edit-2
            5 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.

          • TechNom (nobody)@programming.dev
            link
            fedilink
            English
            arrow-up
            0
            ·
            edit-2
            5 months ago

            Google has discovered that FOSS software under their full control is better than pure proprietary software for monopoly abuse and rent seeking. With FOSS software, they enjoy the automatic popularity that they otherwise would have had to market very hard for. At the same time, none of Google’s free software is truly free. Google devs regularly neglect and reject overwhelming user requirements (jpegxl in chrome is probably the best example of this) and choose designs that clearly favor the company monetarily. It isn’t even practical for normal people to fork their projects.

            Google often uses their ‘FOSS’ projects to twist open standards or the market to their advantage. Android and Chrome are very significant players in this regard. Using Chrome, Google even managed to make the W3C standard too complicated for others to make alternative browsers easily. Google has similar ambitions in the multimedia market. They want to replace the monopolistic media formats with quasi-monopolistic formats like webp and av1 instead of truly open ones like jpegxl.