Hacker News Reader

Comment by pythonaut_16 | Hacker News Reader

The user isn't the problem, the developer is.

If you're developing against Chrome/Chromium, particularly "works in Chrome" instead of developing against the published Web standards, you're support Google & Chrome.

View on HN

The developers decisions are influenced a lot on marketshare. Non-Chrome/Blink being more common will make "Works in Chrome" development less common.

That's fair but you can easily develop for the majority Chrome marketshare by focusing on designing and building your applications on top of the actual web standards instead of Chrome's specific implementations. Probably 95% of the APIs you use in a typical app will be easy to use in a standard way anyway.

WebRTC and some of the more mercurial APIs might be a challenge though.

Most developers probably try to do that. But often they only develop on Chrome, and maybe only have automated tests in Chrome (or not at all...). And then when it then breaks for non-Chrome, fixing tends to get lower priority than new features and bug affecting more users.

I like the idea, but where we run into trouble is when the pm comes downstairs and says it looks wrong on his computer. He uses chrome. He rejects the story. Arguments about correct are moot. Everyone uses chrome is his trump card. The business perspective doesn't care about web standards.

This is not wrong, but you're missing the reciprocity.

Devs don't optimize for Chrome because they're evil, they do it because a vast majority of users use Chrome and they know that. So both parties can do their part.

Reply on news.ycombinator.com