@wycats Though, you might have to settle for the lowest common denominator. Even more important to keep the pressure on standardization.
-
-
Replying to @moritzheiber
@moritzheiber Browsers should experiment the hell out of things, but go-it-alone behavior actually results in slower uptake than discussion.1 reply 13 retweets 4 likes -
Replying to @moritzheiber
@moritzheiber@wycats So we end up with either bad APIs, but shipped, or languish in SDOs while more and more cooks add seasoning for flavor2 replies 1 retweet 0 likes -
Replying to @sleevi_
@sleevi_@moritzheiber And the more you can avoid future hostility, the better, obviously.4 replies 0 retweets 0 likes -
Replying to @wycats
@wycats@moritzheiber If I could do it again, I would have done WebCrypto API as a Chrome extension API, ship it, then bring it to W3C.1 reply 0 retweets 0 likes -
Replying to @sleevi_3 replies 0 retweets 2 likes
-
Replying to @wycats
@wycats@moritzheiber I (now) favor go it alone precisely because designs by committee have lead to dozens of wildly diff APIs, and ...2 replies 0 retweets 0 likes -
Replying to @sleevi_
@sleevi_@moritzheiber Go-it-alone is basically a bullying tactic, and people reflexively deploy counter-bullying tactics.3 replies 6 retweets 2 likes -
Replying to @wycats
@wycats@moritzheiber But it is, in part, a reaction to overreaching SDOs staffed without actual devs. I'd wager 75% of WC WG has no JS exp3 replies 0 retweets 1 like
@sleevi_ @moritzheiber Agreed. But you're not going to get a lot of other browser uptake by shipping-and-insisting.
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.