Hacker News new | past | comments | ask | show | jobs | submit login

Now people write for chrome, and then spend hours hacking them to support web standards.



More like Chrome is the Web Standard now. Generally stuff that runs in chrome, runs fine in Firefox and Edge, Safari can be a little weird sometimes but overall it's way easier these days.


There are some fine differences. Google likes to blur the line between actual Web standards (which have consensus via W3C or WHATWG), Chrome's prototypes that may inform future standards, and self-serving Google APIs that only have "Web" in their name.

Sometimes it's just Google releasing whatever they want, use it on google.com and youtube.com while serving slower/buggier fallbacks to others, so other vendors have no choice but to implement Google's non-standard invention to avoid looking broken.

Google gets away with this a lot, because there are also many actual standards that Safari is ignoring. Without following dozens of mailing lists and bug trackers it's hard to tell what Google is pushing for themselves (e.g. AMP was a motivation for many "standards" proposals), and where others are dragging their feet.


> Google gets away with this a lot

I think the point seen here is really that if the standards org doesn't impact the browsers and the browser in question has greater than 60% market share then that browser is the standards org and the W3C doesn't matter. Who is going to harm Google? How would the W3C enforce their standards? If most of your users are on Chrome and Chrome sets the feature set rather than the W3C, why wouldn't you just build to Chrome?


Browser vendors have always been driving the standards. W3C is correct to call their docs "recommendations".

There was a brief nice moment in history when WebKit, Gecko, Trident, and Presto each had enough market share that all the vendors had to cooperate.

Nowadays Trident and Presto are dead. Gecko is a great engine, but doesn't have enough market share to veto anything. So Blink can ship anything and claim it's supported "everywhere except Safari".


The W3C gave up on many web standards like HTML and their process is just rubber stamping whatever WHATWG decides are standards and WHATWG seems to just rubber stamp whatever Google wants (more often than not).




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: