dpark 2 days ago

This is a vacuous statement. No one is stopping me from using JPEG XL in the same sense that no one is stopping me from using DIMG10K, a format I just invented. But if I attempt to use either of these in my website today, Chrome will not render them.

In a very real sense Google is currently stopping web authors from using JPEG XL.

Reply View 4 replies
  • jeffbee 2 days ago

    The web was designed from the start to solve this problem and you can serve alternate formats to user agents which will select the one they support.

    Reply View 3 replies
    • dpark 2 days ago

      Your statement here amounts to “you can serve JPEG XL to other browsers, just not Chrome”.

      Yeah, that’s what I said.

      Reply View 2 replies
      • jeffbee 2 days ago

        This is the way of web. Sites don't get to dictate what the user agent does. The clue is in the name: user agent.

        Reply View 1 reply
        • dpark 2 days ago

          Okay. So putting it together…

          If the user agent does not support JPEG XL, then you cannot use it.

          “Nobody is stopping you from using jpegxl” except Google.

          Reply View 0 replies
xg15 2 days ago

Then what is this article about?

Reply View 1 reply
  • jeffbee 2 days ago

    It's a meta-commentary about the death of critical thinking and the ease with which mindless mobs can be whipped.

    From the jump, the article commits a logical error, suggesting that Google killed jpegxl because it favors avif, which is "homegrown". jpegxl, of course, was also written by Google, so this sentence isn't even internally consistent.

    Reply View 0 replies