It seems like I need to be more explicit part 3 in -- specifically for webdevs -- in my blog post series about standards (a small thread): https://infrequently.org/2018/06/effective-standards-work-part-1-the-lay-of-the-land/ … https://infrequently.org/2018/06/effective-standards-work-part-2-threading-the-needle/ …
-
-
With IE6, MS also just did whatever the fuck they wanted outside of a standards process. This response from you unfortunately very telling. I don't know if you were around for the browser wars or not, but it feels like you didn't learn from them.
-
Did you ever develop anything on/for NN4? It was the concurrent competition during the IE4-6 dev cycles. Counterfactuals matter. Netscape did what they damned well pleased, and it was horrifying.
- 6 more replies
New conversation -
-
-
Don't get me wrong, it very much overstayed it's welcome, and standards helped clean up the vbscript/ActiveX-caused messes. I worked in Chrome Frame *explicitly* to show it the door. But the rose colored glasses don't help. Did you ever try doing anything in NN4?
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.