Hacker News Reader

Comment by Retr0id | Hacker News Reader

A polyfill (in the form of a wasm blob that implements the decoder) would be an interesting solution at least, since it would make the chrome experience noticeably worse than any competitor that has native support.

View on HN

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.)

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

> 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.

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

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

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

And Firefox

and here's one: https://github.com/niutech/jxl.js

Then again - with Chrome being the most popular browser - websites might not want to introduce a solution that results in worse performance for the majority of their users.

Google was able to leverage Youtube against Firefox, since people have few alternatives.

Reply on news.ycombinator.com