@slightlylate @vivainio @miketaylr I'm not super-interested in this apologia. "Best Viewed in Chrome" is not good, even sort of.
-
-
Replying to @wycats
@wycats: got me! I spend my time making an interoperable web in the future possible as a ruse! O_o /cc@vivainio@miketaylr1 reply 0 retweets 0 likes -
Replying to @slightlylate
@slightlylate@wycats@vivainio@miketaylr "best in chrome" is not an interoperable web though3 replies 0 retweets 0 likes -
Replying to @jacobrossi
@jacobrossi: I should know better than trying to get people to consider more than one concept at once. /cc@wycats@vivainio@miketaylr1 reply 0 retweets 0 likes -
Replying to @slightlylate
@slightlylate@wycats@vivainio@miketaylr reading back through, you didn't say that. though in the twitter stream readers might think that.1 reply 0 retweets 0 likes -
Replying to @jacobrossi
@jacobrossi: as someone who did a lot of cleanup from the birth phase, I'd hope I never imply it either. /cc@wycats@vivainio@miketaylr1 reply 0 retweets 0 likes -
Replying to @slightlylate
@slightlylate to clarify then, do you think a "best in chrome" web beating native is still a win? /cc@wycats@vivainio@miketaylr1 reply 0 retweets 0 likes -
Replying to @jacobrossi
@jacobrossi certainly not. But success could start there, as it did with IE4. /cc@wycats@vivainio@miketaylr1 reply 0 retweets 0 likes -
Replying to @slightlylate
@slightlylate I'd prefer not or else we spend the time after that fixing the modern "IE6isms" of Chrome/Safari@wycats@vivainio@miketaylr1 reply 0 retweets 0 likes -
Replying to @jacobrossi
@jacobrossi : me either. My diagnosis is that IE6 "went bad" because MSFT left. It in the sun too long /cc@wycats@vivainio@miketaylr2 replies 0 retweets 0 likes
@slightlylate @jacobrossi @vivainio @miketaylr actually, that's the only reason the web survived with more than one impl.
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.