Antitrust Law Is Supposed To Protect Consumers, Not Competitors
from the blast-from-the-past dept
Opera has filed a complaint in Europe accusing Microsoft of violating antitrust laws there. The arguments in this complaint appear to be very similar to the arguments in the original antitrust case against Microsoft a decade ago, which some states are still pushing here in the United States. I don't know much about European antitrust law, but it's a little hard to take Opera's policy argument seriously. Mozilla has reported that Firefox's market share is 28 percent in Europe, a number that has been growing steadily for most of this decade. And Apple recently joined the fray by launching a Windows version of its Safari browser. There is, in short, no shortage of competition in the browser market, and that's been reflected in the steady erosion of Microsoft's market share. Now, it is true that the situation is somewhat unfair to Opera. Microsoft's ability to bundle Internet explorer with Windows obviously gives it a big advantage (as does Apple's ability to bundle Safari with Macs and iPhones). But antitrust law was never designed to make the market "fair" in this sense, and as Firefox demonstrates, those disadvantages are far from insurmountable. Antitrust law is about protecting consumers, not competitors. As far as I can see, there's nothing stopping consumers who are dissatisfied with Internet Explorer from downloading Firefox, Safari, or Opera. Indeed, a quarter of European Internet users have done just that. Perhaps the money Opera is currently spending on lawyers would be better spent on figuring out why Mozilla has been so much more successful than Opera at attracting new users.Thank you for reading this Techdirt post. With so many things competing for everyone’s attention these days, we really appreciate you giving us your time. We work hard every day to put quality content out there for our community.
Techdirt is one of the few remaining truly independent media outlets. We do not have a giant corporation behind us, and we rely heavily on our community to support us, in an age when advertisers are increasingly uninterested in sponsoring small, independent sites — especially a site like ours that is unwilling to pull punches in its reporting and analysis.
While other websites have resorted to paywalls, registration requirements, and increasingly annoying/intrusive advertising, we have always kept Techdirt open and available to anyone. But in order to continue doing so, we need your support. We offer a variety of ways for our readers to support us, from direct donations to special subscriptions and cool merchandise — and every little bit helps. Thank you.
–The Techdirt Team
Filed Under: antitrust, europe, ie
Companies: microsoft, opera
Reader Comments
Subscribe: RSS
View by: Time | Thread
hmm
From the EU side, the latest antitrust lawsuit opened the floodgates to stuff like this, so on that side of the pond it is open grounds to hit MS for stuff like this. Groklaw references that well here -> http://www.groklaw.net/article.php?story=20071213104023255
Personally, an unbundling, or forcing of options of what browser makes perfect sense on a "supposedly-open" proprietary system such as Windows. That is, as long as you don't only have the choices of "Microsoft A", or "Microsoft B". Apple always ships 1 specific browser with their system, and you don't hear of 80 million problems with it, no? (same for linux and/or anything else that fixes problems much faster). So why should IE be given the excuse on that?
[ link to this | view in thread ]
Missed the point
[ link to this | view in thread ]
it is antitrust
MS still keeps a high market share by forcing users to use IE in order to do any windows or office updates. This is obviously a way to keep their market shares up, which should or may be illegal
[ link to this | view in thread ]
Re: it is antitrust
Antitrust is supposed to stop monopolistic behaviors. If there's serious competition it's hard to see how there's an argument that you have a monopoly.
The problem isn't that there is nothing else available, it is that Microsoft makes it seem like there is nothing else available.
That would be a lot more convincing without the numbers Tim noted in the post. Other browsers have significant marketshare.
MS still keeps a high market share by forcing users to use IE in order to do any windows or office updates. This is obviously a way to keep their market shares up, which should or may be illegal
But does it hurt consumers? Who cares if it bumps up their share numbers if the overall impact is minimal on consumers?
[ link to this | view in thread ]
Hmm...
[ link to this | view in thread ]
Re: Re: it is antitrust
[ link to this | view in thread ]
But wait...
Okay then, should they bundle their competitors browsers? Why? Who's going to reimburse them for the expense of adding the other browsers? Mozilla won't want to: nor Apple, nor Opera, nor anyone else, I'm sure.
[ link to this | view in thread ]
Here's my take: Firefox has always been free, while Opera was trialware until 2000 and ad-sponsored until 2005? When you've got a choice between IE (crappy, no ads), Mozilla/Firefox (great, no ads) and Opera (great, with ads) it's no surprise why Opera has been slow to gain market share. A lot of Mozilla/Firefox users migrated years ago and the position Firefox is in now is not one you get to without serious momentum. I think Opera's biggest mistake was not going completely free a long time ago. I've talked to people who thought Opera still had ads or was even still trialware! They could use some better marketing.
Widespread adoption by the open source community is also probably a large factor in Firefox's success.
[ link to this | view in thread ]
If I don't know how to do this readily I'm betting 95%+ of the computer using public wouldn't know where to start.
[ link to this | view in thread ]
Re: But wait...
At the moment that the practice doesn't hurt customers the antitrust laws should not be applicable.
Additionally, there is no reason why Microsoft should bundle their competitors browsers, nobody would pay them for the expense.
This is all about companies that want to earn in the court what they haven't earned by building a better product. And about greedy lawyers that see the opportunity to make some good bucks just because the name Microsoft is involved.
Just an illustration of what I mean better products: I have been trying the use of Opera in a MotoQ smartphone (most people in the area know that Pocket IE is very limited). Well, the software is installed in the phone without a decent users manual, without a decent help, and has a number of keys on the keyboard marked as special functions so that when the user presses those keys in order to fill a field in the screen the software responds in the most strange ways. It turns out that before filling forms in the browser you need to press a specific key in order to turn-off the special shortcuts mode. THIS IS USER-HOSTILE !!! I don't know if in Opera for PC it also exists, but it is clear that whoever programmed that thought as a programmer, not as a user.
I would suggest that Microsoft would stop bundling the Explorer in Windows, and instead of that, would bundle 3 menu links: Download IE, download Opera, download Mozilla - believe me, the market shares would stay nearly the same.
[ link to this | view in thread ]
It's not the bundling that's the issue
While IE continues using proprietary means to provide what could be provided using standards-based technologies, and continues to have dominant marketshare, developers have to restrict development to the lowest common denominator--IE.
What this does is undercut the efforts the other browser creators make implementing the standards, undervaluing their work while Microsoft blithely continues doing its own proprietary thing.
MS has representatives on the standards teams, but makes absolutely no promise to support the standards. Instead, the company focuses more on undercutting those same standards. It's almost like Microsoft attends the meetings to see what the other browser creators will be doing, and then goes back and does its own thing.
In the meantime, the state of art does not grow because we're held back by Microsoft's determination to undercut the standards and force IE proprietary approaches.
All of this combined sure strikes me as antitrust behavior. We should be supporting Opera, not condemning it.
[ link to this | view in thread ]
Re: It's not the bundling that's the issue
I don't know, the state of the art in web development sure seems to have advanced in the last few years. Ajax programming techniques, for example, seem to have grown out of changes pushed by Microsoft in the late 1990s. It's certainly conceivable that things would have advanced faster if Microsoft did a better job of paying attention to standards, but do we really want a European judge in the position of dictating which features IE has to support?
[ link to this | view in thread ]
no browser?
It's called Automatic Updates. I don't even have iexplore.exe on my computer (removed from my Windows install CD, so it's never there), yet am fully patched. If you prefer an actual program rather than a Control Panel applet, I recommend Daisy [ http://vtntug.w2k.vt.edu/daisy.htm ](XP and earlier only.)
For better or for worse, the internet can be accessed on a Windows machine without a browser very simply, due to IE's deep integration with the operating system: Simply enter the URL in the address bar of any Windows Explorer window. That integration is a major security flaw, but it's there and can be used once to visit getfirefox.com or whatever you prefer.
[ link to this | view in thread ]
Re: It's not the bundling that's the issue
I have FireFox at home, I don't use it too often but it douse serve a function. I can see the web sites just as good with FireFox as with IE.
To point agean at bundling, Linux bundles FireFox, MAC bundles Safari. The bundling claim should not be involved in any way.
[ link to this | view in thread ]
Re: Re: It's not the bundling that's the issue
1. Back in the early to mid 90's when all other browsers were adding support for CSS, MS stopped all real development on IE, letting it languish as an HTML-only platform until the release of IE 5 in 2000 - an eternity in web-years (some will argue IE 3-4 had CSS but the implementation was so buggy and incomplete, I defy anyone to show me a CSS page that worked with it). Consequently, every web page created using CSS also had to have an IE HTML-only version - thus doubling (or more) the level of effort needed to launch a web site.
With the release of IE 5 & 6, MS implemented an incorrect box model, and an non-standard DOM, again requiring programmers to write multiple versions of everything.
Lest anyone get there knickers in a twist, yes, other browsers have had many instances of bad or incomplete implementations - the difference is those browser developers a.) worked with the standards groups to iron-out differences, and b.) released regular updates to fix the problems web developers encountered. Not so with MS.
2. You may not remember Sun Micro's law suit with MS over Java. MS took the Java platform and modified it into a Windows-only implementation, so that all Java development on Windows would only work with Windows and IE. In a decision that stunned the web community, the court apparently failed to understand public licensing and allowed MS to get away with it.
3. Even HTML was modified. Pick up any HTML reference and you will see a section of IE-only commands. For a while, other browser developers did the same, but due to the unfavorable response from web programmers, everyone but IE stopped implementing proprietary command structures.
There is far too much to go into here, but that should at least give you a brief understanding of the annoyance MS has caused programmers for years. Opera's contention that some programmers/companies are not willing to do multiple versions of every site and therefore only develop IE versions is probably correct.
[ link to this | view in thread ]
Re: Re: It's not the bundling that's the issue
1. Back in the early to mid 90's when all other browsers were adding support for CSS, MS stopped all real development on IE, letting it languish as an HTML-only platform until the release of IE 5 in 2000 - an eternity in web-years (some will argue IE 3-4 had CSS but the implementation was so buggy and incomplete, I defy anyone to show me a CSS page that worked with it). Consequently, every web page created using CSS also had to have an IE HTML-only version - thus doubling (or more) the level of effort needed to launch a web site.
With the release of IE 5 & 6, MS implemented an incorrect box model, and an non-standard DOM, again requiring programmers to write multiple versions of everything.
Lest anyone get there knickers in a twist, yes, other browsers have had many instances of bad or incomplete implementations - the difference is those browser developers a.) worked with the standards groups to iron-out differences, and b.) released regular updates to fix the problems web developers encountered. Not so with MS.
2. You may not remember Sun Micro's law suit with MS over Java. MS took the Java platform and modified it into a Windows-only implementation, so that all Java development on Windows would only work with Windows and IE. In a decision that stunned the web community, the court apparently failed to understand public licensing and allowed MS to get away with it.
3. Even HTML was modified. Pick up any HTML reference and you will see a section of IE-only commands. For a while, other browser developers did the same, but due to the unfavorable response from web programmers, everyone but IE stopped implementing proprietary command structures.
There is far too much to go into here, but that should at least give you a brief understanding of the annoyance MS has caused programmers for years. Opera's contention that some programmers/companies are not willing to do multiple versions of every site and therefore only develop IE versions is probably correct.
[ link to this | view in thread ]
Re: Re: It's not the bundling that's the issue
1. Back in the early to mid 90's when all other browsers were adding support for CSS, MS stopped all real development on IE, letting it languish as an HTML-only platform until the release of IE 5 in 2000 - an eternity in web-years (some will argue IE 3-4 had CSS but the implementation was so buggy and incomplete, I defy anyone to show me a CSS page that worked with it). Consequently, every web page created using CSS also had to have an IE HTML-only version - thus doubling (or more) the level of effort needed to launch a web site.
With the release of IE 5 & 6, MS implemented an incorrect box model, and an non-standard DOM, again requiring programmers to write multiple versions of everything.
Lest anyone get there knickers in a twist, yes, other browsers have had many instances of bad or incomplete implementations - the difference is those browser developers a.) worked with the standards groups to iron-out differences, and b.) released regular updates to fix the problems web developers encountered. Not so with MS.
2. You may not remember Sun Micro's law suit with MS over Java. MS took the Java platform and modified it into a Windows-only implementation, so that all Java development on Windows would only work with Windows and IE. In a decision that stunned the web community, the court apparently failed to understand public licensing and allowed MS to get away with it.
3. Even HTML was modified. Pick up any HTML reference and you will see a section of IE-only commands. For a while, other browser developers did the same, but due to the unfavorable response from web programmers, everyone but IE stopped implementing proprietary command structures.
There is far too much to go into here, but that should at least give you a brief understanding of the annoyance MS has caused programmers for years. Opera's contention that some programmers/companies are not willing to do multiple versions of every site and therefore only develop IE versions is probably correct.
[ link to this | view in thread ]
It IS anti-trust, and it does prevent a free marke
And Tim, you have brought the issue of Firefox's share. How did it reach the share? Open source community and active advertisement and backing by Google. The IE vs Firefox wars were actually a proxy for Microsoft vs Google. And even after that, with an effort of quite a few years, and a better browser, Firefox has reached only about 15% worldwide. So, that is your excuse for competition? That any browser has to have a 700 pound giant as a friend even to have a moderate success, after spending billions of dollars and a few years, in addition to a far superior product?
[ link to this | view in thread ]