Understanding the Internet Explorer Problem
Lot's of my Microsoft friendly friends (and yes, I'm among the Microsoft friendly folks when it comes to technology) don't understand the issue most of the technical community has with the abuse Microsoft has been allowed to get away with and would like you to think that this is all about someone else deciding what is best for you.
They would like you to believe that Firefox, Opera, etc know better in requesting that Internet Explorer be removed from the OS. There is no basis for this argument because if they feel they need IE, they can download it free of charge.
What is at stake here is the functionality of web services, which is generally agreed to be the future. Microsoft should not be allowed an inch of competitive advantage for their existing platform, not only because they obtained it in a dirty anticompetitive way, but because their prior behavior indicates they have little interest for anyone but themselves.
And when you're asking for the world to trust you with their data, you need to be a little more accommodating.
That is what Firefox, Opera, Safari and all others need to push not just EU but also US legislation to do - Microsoft should not be given a free pass on their past transgressions of trying to own open Internet protocols and apply what they have learned from screwing OEMs and VARs into screwing the consumer at large.
If you like IE, download IE. If you like Firefox, download Firefox. If you like Safari, download Safari. If there is more choice in the platform, it stands to reason that there will be more choice and interoperability for services.

And the average user will know how to download a browser without having a browser?
I think its pretty fundamental to have a browswer as part of the OS, if they dont like IE, there is nothing stopping them from downloading another browser. My personal opinion though.
Run Server core. Now download a browser. Oh right, it's command line. It doesn't work that way.
I haven't met an OEM computer yet that doesn't have any number of third party financial deals loaded up on boot. None of these companies have any interest in anyone but themselves. It's called capitalism last I checked and many firms abide by this mantra.
You have seen how IE is integrated in the OS so the request to pull it out would be we'd all be running the equivalent of Server Core, right? Think of your ask. Now ask it of all of the platforms out there to be a true level playing field.
How about some more competition shall we? How about removing Safari and Quicktime from Apple? Oh wait, you can't, can you? Quicktime in particular is embedded in the OS. Shouldn't they too be on a level playing field for all their past deeds represents they only care about themselves? Back dating stock options and what not? Oh and how about how they too screwed OEM and VARs. Oh wait! They don't have any OEM and VARs because they sue anyone trying to build their hardware and they don't have a partner program.
People 'are' making the choice and the browser wars showcase this.
If you want Safari, buy Apple. If you want Firefox, buy Ubuntu. Why can't I choose to run IE on either one of those? Competition swings both ways.
I'm still waiting for the day that it's legal for me to fire up a vmware version of a Mac OS on something other than an Apple piece of hardware. Let's talk about more choices and operability there for a start, shall we?
I like lynx because it's a bit easier than straight telnet and saves me a crapload of bandwidth.
I still don't understand why help desk staff think I'm crazy when I log a fault with their web site. Some people...
Susan,
I agree that Apple gets away with far too much.
But the more these companies are allowed to grab and lock in their audience in their proprietary systems, the worse off we are, not better. So should Apple get the same smackdown - absolutely. But allowing a criminally abused monopoly to try again is quite opposite of reasonable.
-Vlad
Susan,
Why hasn't Microsoft chosen to make IE for any of those platforms, especially Linux?
The matter of need a browser initially for the every day user is the big problem. The bigger problem is Microsoft accepting open standards. If Microsoft were to base IE on the actual open standards instead of its own versions of these standards, I don't think you would see as much complaining. The fact that you can make a page that will work in IE but not completely work in Firefox, Opera, or Safari, is a testament to that.
Mike,
IE8 is based on open web standards...
Wayne,
I along with a few others in my office have been playing with IE8 and it still breaks too much. Too many issues with sites not working properly, and is it true open standards or Microsoft versions of them.
Some things Microsoft does right, and some things they do wrong.
do those sites work in IE8 when you do IE7 compatibility mode?
its possible those sites were created with IE7 in mind and hence dont work with the open standards taht IE8 is now using, but I agree this probably should have been done all along so there wouldnt be a need for "IE7 compat mode"
Web developers wrote their web sites for non standard IE 7, 6, 5, 4 etc etc and now are having to rewrite for the standards based IE 8.
IE8 is based on standards, and because everyone wrote for non standard IE7 the web sites won't work without the compatibility.
http://blogs.zdnet.com/microsoft/?p=1057
http://www.webstandards.org/2007/12/19/ie8-passes-acid2-test-2/
I think people talking about standards probably should go read them and then think hard about how they would implement them.
The biggest problem in the past was there was too much room for interpretation on how the implementation should behave. That behaviour has been narrowed down in later iterations of the various standards with the aid of various working groups and conferences, but these attempts are no panacea to the presentation behaviour problem.
The reason we have Safari and now Chrome is one of branding and developer control. It has nothing to do with making Web developers life easier.
The Web services layer really is just another remoting API. The real issue is the presentation layer - this is where the turf wars are being fought and this is where all the complexity and developer abuse occurs. It's the X-Windows + windows manager war all over again.