3 ms·
This is a fascinating read, but this one line stuck out to me: > Scott told me that the IE team had over 1,000 people What on earth could they possibly have h
by smcl 12y ago
This is a fascinating read, but this one line stuck out to me:
> Scott told me that the IE team had over 1,000 people
What on earth could they possibly have had those thousand people doing?
- tonyedgecombe 12y agoI expect 990 of them were supervising the 10 that did all the work.
- chris_wot 12y agoThey were basically trying to figure out how to "integrate" the browser into Windows. But there were vast amounts of technology based around or that used ActiveX - ADO, ASP, ASF, you name it - Microsoft created it. Besides that, there were a lot of standards they were integrating.
- scholia 12y agoAt some points, Microsoft had two teams working on different versions of IE, in order to leapfrog Netscape. The extra team developed the "componentized" version where the browser was built from re-usable objects, where Netscape's code was still a rambling mess. (This helped Microsoft win the AOL business: it used IE even after it bought Netscape.) The US DoJ's Janet Reno was a major factor. She forced Microsoft to sign a Consent Decree (1995?) that prevented Microsoft from tying separate products to Windows but allowed it to provide integrated improvements. The DoJ followed up with an anti-trust suit (on Netscape's behalf) over browser tying. Microsoft won the browser case by 2-1 on appeal. However, all this bloodletting may have been a factor in Microsoft putting off the next browser, which eventually appeared in Vista. Which was late, following the Longhorn debacle, which prolonged XP's life, which enabled IE6 to get entrenched, which caused web designers so much pain. The world might be a better place if the DoJ hadn't interfered, but we'll never know....
- jordanlev 12y agoIf you haven't already, you should definitely read "How Microsoft Lost The API War" (http://www.joelonsoftware.com/articles/APIWar.html http://www.joelonsoftware.com/articles/APIWar.html) by Joel Spolsky. One of my favorite articles of all time -- it speaks to some of the things you raised... specifically how Microsoft intentionally let IE6 development come to a halt because it was no longer strategically beneficial to them (not because the DoJ interference made them stop). Also hints at the idea that the stability of IE6 for a while actually created a good environment for innovation in the web app space to take place because things we're changing all the time.
- scholia 12y agoGreat point, I'd missed that. Even though I'm a huge Spolsky fan, read the whole website, bought the book, interviewed the man etc ;-) Otherwise, I'd have picked his first Bill Gates review as one of my favorite articles of all time...
- deleted 12y ago[deleted]
- nly 12y agoIt is indeed absolutely mind-boggling when you consider that MS later did next to nothing on the browser for 5 years. Hell, Apple forked KHTML in 2001, a few months before the release of IE6, and had 5 whole years to develop Safari (and WebKit) with essentially no significant (Sorry Opera) commercial competition. In fact, between 2001 and late 2004 (FF 1.0) no Netscape progeny had significant share, so Microsoft had no real competition of any sort. If MS had kept their foot on the gas we may never have seen an opportunity for Chrome to dominate.
- pcwalton 12y agoIE6 had a lot of features, many of which are obscure now, but which took a long time to be replicated by the standards. Consider "zoom" (like a subset of CSS transforms), "filter" (a combination of CSS transforms, text-shadow, box-shadow, and CSS filters), page transitions (like CSS transitions, sorta), colored scrollbars, and so on. There were also random features like smart tags that are best forgotten…
- DonHopkins 12y agoNot to mention Dynamic HTML Behavior Components, that let you implement COM components in JavaScript.
- DonHopkins 12y agoQuerying each other's interfaces and aggregating with the controlling IUnknown.