@slightlylate @sideshowbarker W3C's HTML was horrendous, obvs. CSS, despite its flaws, is one of the most successful WGs.
-
-
Replying to @tabatkins
@tabatkins@sideshowbarker: dead weight loss says otherwise. Corners have turned, etc. etc., but we cannot call last decade "good"1 reply 0 retweets 0 likes -
Replying to @slightlylate
@slightlylate@sideshowbarker CSSWG produced many great specs, with great adoption and webdev love. Big problems too, of course, but...1 reply 0 retweets 0 likes -
Replying to @tabatkins
@slightlylate@sideshowbarker ...within the W3C it was one of the most successful, well-run WGs. (Which is saying something...)1 reply 0 retweets 0 likes -
Replying to @tabatkins
@tabatkins@sideshowbarker: it's damning with faint praise? Sorry, but not biting. Lets talk about variables, shall we?1 reply 0 retweets 0 likes -
Replying to @slightlylate
@slightlylate@sideshowbarker Which occurred? And in a better form than previous proposals, due to baking and watching innovation outside?1 reply 0 retweets 0 likes -
Replying to @tabatkins
@tabatkins: note well: progress delayed is progress denied /cc@sideshowbarker1 reply 0 retweets 0 likes -
Replying to @slightlylate
@slightlylate@sideshowbarker Yes, thus the "Big problems too, of course". CSS isn't to be emulated, but it also did better than most of W3C1 reply 0 retweets 0 likes -
Replying to @tabatkins
@tabatkins@sideshowbarker: so OK, damning with faint praise ;-)1 reply 0 retweets 0 likes -
Replying to @slightlylate
@slightlylate@sideshowbarker Yeah, mainly just pointing out that CSSWG isn't the best example of "W3C is totes broken". ^_^2 replies 0 retweets 1 like
@tabatkins @sideshowbarker: OK, not best, but it'll do.
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.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.