year in, year out, the w3c would find the folk who could exhaust everyone else over mailing lists and set the standard to be
-
Show this thread
-
the w3c tried a http/2 first, decades prior, influenced by CORBA, then XHTML, and eventually whatwg happened
1 reply 0 retweets 3 likesShow this thread -
or "it's nice that you keep adding implementation specs but um we're gonna document what we build"
1 reply 0 retweets 5 likesShow this thread -
the thing is, what browsers do is kinda far more strongly specified now—even the recovery when parsing html is defined
1 reply 0 retweets 4 likesShow this thread -
even if microsoft did choose to play catchup with chrome, they'd only be reimplementing 90% of it
1 reply 0 retweets 3 likesShow this thread -
the open web has always been this imaginary concept we had and lost, echoes of slashdot lamenting that the web should be done the right way
1 reply 1 retweet 7 likesShow this thread -
i guess i'm saying that a lot of people get angry when they discover the power structures behind the alleged meritocracy
1 reply 0 retweets 9 likesShow this thread -
or, as much as you can kick and scream for microsoft to keep updating the browser, no-one uses it, tests against it
1 reply 0 retweets 2 likesShow this thread -
meanwhile, chromium, v8 are open source and i haven't had to run realplayer or shockwave or flash in forever so ???
1 reply 0 retweets 4 likesShow this thread -
rip internet explorer, you were right about the box model
1 reply 0 retweets 10 likesShow this thread
And Pointer Events. And ORTC. Good engineering.
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.