Hacker News Reader

A standard is only a standard when there is more than one implementation. Chrome DRM or Chrome RTC are no better than ActiveX, except for hindsight (_now_ it is obvious ActiveX is crap).

The central point is avoiding lock-in, with the long term objective of maintaining a competitive browser landscape. Code for one browser, and we'll be collectively screwed when Chrome development reaches Google Reader status.

View on HN

A standard is whatever goes into https://html.spec.whatwg.org . Period.

CSS Flex is a standard. If Konqueror, Firefox, Edge, or whatever other browser doesn't support it (I know they support it now, but that wasn't the case 2 or 3 years ago), it's not any of my business. I'll keep using Flex because it's an accepted standard. And my webpages will work on any browser that supports that standard. If that means that my website works only on Webkit-based browsers, well, then that's really not up to me to fix, isn't it? That is something that the people behind other browsers should fix, by implementing "Flex".

This is just the latest iteration of the age old "fix your code" vs "no, fix your compiler" argument.

it's not any of my business.

So what is your business?

Reply on news.ycombinator.com