Chrome still hasn't changed its opinion about dropping JPEG XL support

Re:Chrome still hasn't changed its opinion about dropping JP... by dcow on Tuesday June 06, 2023 @12:14PM (#36215034)

Now all that's left is to generalize that and start a movement where we kill Chrome by making commonly used JS frameworks deliberately perform orders of magnitude worse on Chrome. (I understand I'm being absurd and that your suggestion is not actively malicious like mine is because Chrome is being stubborn in this case.)

[ Parent | on HN ]

Re:Chrome still hasn't changed its opinion about dropping JP... by WorldMaker on Tuesday June 06, 2023 @12:54PM (#36215721)

It worked for YouTube helping get Chrome adopted in the first place. (I kid, mostly.)

[ Parent | on HN ]

Re:Chrome still hasn't changed its opinion about dropping JP... by marcosdumay on Tuesday June 06, 2023 @12:59PM (#36215798)

> I understand I'm being absurd

Huh? Up to that point I was expecting a joke about Chrome being the receiver of the exact same thing Google practices.

[ Parent | on HN ]

Re:Chrome still hasn't changed its opinion about dropping JP... by StrangeATractor on Tuesday June 06, 2023 @02:28PM (#36217089)

That's not so outrageous, Google gives you different search experiences based on your user agent.

[ Parent | on HN ]

Re:Chrome still hasn't changed its opinion about dropping JP... by bmacho on Tuesday June 06, 2023 @02:42PM (#36217258)

No, don't do that, but make google to support the best possible technologies at least.

[ Parent | on HN ]

Re:Chrome still hasn't changed its opinion about dropping JP... by devwastaken on Tuesday June 06, 2023 @04:34PM (#36218741)

You can't kill chrome because there is no alternate tech. Everything is chromium, or follows it (except safari).

[ Parent | on HN ]

Re:Chrome still hasn't changed its opinion about dropping JP... by BadBadJellyBean on Tuesday June 06, 2023 @04:48PM (#36218906)

And Firefox

[ Parent | on HN ]