@bz_moz Isn't Chrome the specification everybody should follow?
-
-
Replying to @FremyCompany
@FremyCompany Well, Google's marketing folks certainly see it that way, sure.1 reply 0 retweets 0 likes -
Replying to @really_bz
@bz_moz I'm not even sure we should blame them for that. This is what most web devs I know seem to think anyway.1 reply 0 retweets 0 likes -
Replying to @FremyCompany
@FremyCompany Well, that's not an accident. Google and Apple have both been trying really hard to equate "standards" with their impls.2 replies 0 retweets 0 likes -
Replying to @really_bz
@bz_moz When the editors of most specs are from Google, how surprising is that? Standardization involves a certain I-did-it-o-cratie.2 replies 0 retweets 0 likes -
Replying to @FremyCompany
@FremyCompany The key part is not who the editors are, but the explicit "I did it this way, therefore that's the spec" crap.1 reply 0 retweets 0 likes -
Replying to @really_bz
@bz_moz Editors are both human and employee, that's already two factors biasing toward this abuse. I've the same issue with CSS "Variables".2 replies 0 retweets 0 likes
@FremyCompany The editors I've dealt with are fine. It's the developer evangelists and marketing that I have problems with.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.