4 ms·
> That's not really Chrome's fault It's Chrome's fault that it's shipping non-standard things. Not like any browser is blameless here, but let's not pretend t
by bzbarsky 10y ago
> That's not really Chrome's fault
It's Chrome's fault that it's shipping non-standard things. Not like any browser is blameless here, but let's not pretend they're innocent either.
It's _Google's_ fault that it's shipping non-standard things in its browser and then using them in its other products to lock out other browsers.
> We didn't blame Microsoft for "lock-in" back in the IE-only website days
We sure did. And it wasn't even Microsoft creating the IE-only websites!
- sangnoir 10y ago> It's Chrome's fault that it's shipping non-standard things. I challenge you to name one non-niche browser that didn't ship "non-standard things"
- pcwalton 10y agoThe norms have been different in the past few years than during the first browser war. All browser manufacturers have effectively pledged to not ship things without consensus. In the case of NaCl, Google got around their own pledge by declaring NaCl "not part of Blink" and therefore not subject to the Blink rules, which was a cop-out if I've ever seen one.
- bzbarsky 10y agoI explicitly said other browsers have done it too. Chrome has done a lot more promotion of its non-standard things and of course Google as a whole has been using Chrome's non-standard things quite a bit, which is a large part of the problem.