Hacker News new | ask | show | jobs
by vetinari 1183 days ago
Or: parts of the internets are salty, because Google didn't get the message that nowadays it is mandatory to support their shiny toy in Google's product.

Well, Chrome doesn't support bunch of things, and the world didn't end. The usual topic is, that is supports too many things actually, more than it should.
1 comments
gsich 1183 days ago
Not "or". The FUD is real.

The bugreport even states: "There is not enough interest from the entire ecosystem to continue experimenting with JPEG XL". Not sure on how Google "measured" that.

link
izacus 1183 days ago
By looking at their developer which would have to do the work and those developers said "I'm not interested." Then looking at Mozilla developers which said "I'm not interested." Then looking at Safari developers which also said "I'm not interested."

Having developers decide they won't invest into your toy format forever is not FUD.

link
gsich 1183 days ago
In case of Google it is. Haven't looked at others. Mozilla is dependent on Google money, Safari irrelevant.
link
izacus 1183 days ago
I'm not sure you understand what "FUD" means.
link
gsich 1182 days ago
I'll explain it to you. "fear, uncertainty, doubt".

"uncertainty, doubt": "not enough interest from the entire ecosystem to continue experimenting"

"fear": "By removing the flag and the code in M110, it reduces the maintenance burden and allows us to focus on improving existing formats in Chrome"

link
IshKebab 1183 days ago
Honestly I don't think there was much interest before they rejected it.

The news about it being rejected increased JXL's profile tenfold and there's a lot more interest now.

link
Avamander 1183 days ago
It's somewhat similar to H2 Push, which had similar justifications about adoption and interest. When frameworks finally started supporting it to some extent Google expressed their wish to kill the feature, that instantly dissuaded most developers finishing their implementations or from even considering it.

(Not to mention the fact that the developer tooling for H2 Push was terrible to say the least for a long time)

To me it seems Chromium/Google are somewhat out of touch on how slow the web and adoption of new things happens.

In this case, it was also behind an experimental flag, I don't know how the f** they expect people to show interest if it's practically not usable on the web.

link