3 ms·
It is incorrect to conclude that Microsoft's lack of achievement in X implies (1) its lack of ambition for improving X, or (2) [as ancestor suggested] its deter
by davepeck 17y ago
It is incorrect to conclude that Microsoft's lack of achievement in X implies (1) its lack of ambition for improving X, or (2) [as ancestor suggested] its determination to sabotage X.
Is it really so hard to imagine what life on the inside looks like?
Microsoft is a huge institution. There are hundreds of engineers working on IE. Their work is segmented and bucketed. Some poor engineer has probably spent the last several years doing nothing but maintaining the EOT font format. There are reorganizations, new decisions to realign the next release to meet the goals of other teams, etc. Every decision -- at any level -- requires buy-in from multiple parties with overlapping responsibility. There are, in short, too many cooks in the kitchen.
I'm not saying it isn't ridiculous. But this is how it is inside Microsoft.
- bad_user 17y agoLook, apologies for their behavior aren't enough. I know they have good people in there, but the fact is that they are pulling us back. They couldn't get off their asses to work on IE 7 until Firefox became a credible threat. This is the most compelling evidence that Microsoft always thinks about preserving the status-quo instead of advancing the state of the art. It's their decision and their company, but I'm not going to accept apologies for them lightly. They want to change their image, then they should play nicer with their competition and with us. I don't know how they could do that, but off the top of my head ... why not open-source Silverlight to make it a true standard? But they won't do that since they need control. And round and round we go.
- davepeck 17y ago> They couldn't get off their asses to work on IE 7 until Firefox became a credible threat. This is very true and I've always felt it is a strong condemnation of what goes on inside Microsoft. I neglected to mention this sorry bit of history in my posts above mostly because it's a bit old news. Today, IE is a fully-staffed, heavily armed, etc. I don't think I apologized for Microsoft. There is no excuse for having previously shut down IE, or for having such poor execution now that the IE team is back. There are, however, explanations... ones which hopefully help to dispel the myth that Microsoft is, today, intentionally holding the browser back. The truth is much more mundane.