Is Microsoft trying to kill Apache?

Is Microsoft trying to kill Apache?


When the story about Microsoft shelling out $100,000 to Apache for ASF sponsorship broke across my radar it rather tickled my funny bone and my curiosity. When ASF Chairman Jim Jagielski declared that "Microsoft's sponsorship makes it clear that Microsoft "gets it" regarding the ASF" I had a fit of the giggles--and then, like many others, I started to ponder on the reasons why and what it actually meant.

I'm not paranoid, but...

I am largely immune to conspiracy theories. I don't believe that the American government is behind a cover up at Roswell, but I am prepared to believe that when a company with the track record of Microsoft starts insinuating itself with Apache it is not with the well being of others in mind. The phrase "extend, embrace and extinguish" (E3) is virtually synonymous with Microsoft. The beast of Redmond's mercenary joyride down the digital highway is littered with unsuspecting roadkill and you really do start to wonder if Apache will need to re-read the Highway Code. Let's see if we can tease out just what is going on.

It has long been a mantra invoked regularly that "this year is the year of Linux on the desktop" but no-one ever says that about GNU/Linux on the server--because it has been "Linux on the server" for quite some time. Up to June of this year Apache had just over 49% of the server market. That distinction says it all. Microsoft may or may not be concerned about any inroads to its desktop market but it would certainly like to increase its presence in the server market (its FUD in respect of TCO is legendary). The relative stability and security of the GNU/Linux operating system is of course a given and when it runs the Apache web server they seem to have all the aces. This much we know. So what exactly did Microsoft do?

Microsoft buys its way in

For Microsoft that kind of money is the equivalent of that coin you lost down the back of the sofa last week

Thanks to their bloated coffers, funded by the hated Microsoft tax, amongst other things, it was a financial non event for them to stump up the $100,000 per year to become a Platinum sponsor of the Apache Software Foundation. For Microsoft that kind of money is the equivalent of that coin you lost down the back of the sofa last week. It goes towards supporting thirty five projects as well as all the usual administrative and legal expenses. Nothing untoward there. However, when you start to look at the matter of software licences the picture becomes more interesting.

All licences are not equal

Most users of GNU/Linux will be familiar with the GPLv3. It is certainly the most well known but it is not the only one and whilst Richard Stallman and his colleagues are quite evangelical about protecting the unsullied purity of that licence, others are not quite so scrupulous. There are quite a few variations and the Apache software licence is one of them.

The Free Software Foundation (FSF) never accepted that the Apache Licence v2.0 was compatible with the GPLv2 and even though it now acknowledges compatibility between the Apache Licence and the GPLv3 it does not distribute software under that licence. Please, please correct me if I am wrong but it seems that the problems arise because the Apache licence is not viral and does not support Copyleft. (In fact the Apache licence is not even "weak copyleft". It allows for the use of source code for both free and proprietary software) This means that programs written under the GPL could not link to other programs whose libraries were GLP-incompatible.

since Microsoft managed to get OOXML adopted as an ISO standard it tends to leave a bad taste in the mouth. Yes, the good guys lost. Again

Given these differences it is not difficult to see that Microsoft would find Apache a relatively attractive target as it licence is not as restrictive as the GPL.

Clearly Microsoft have not forgotten the profitable lessons from its extinction of the Mosaic browser by Internet Explorer. Like Apache, its open source licence was weak in terms of protecting itself from predatory monopolists like Microsoft who licenced it from Spyglass and then proceeded to shaft them by giving the browser away free, gutting Spyglass's licence revenue.

That adds a whole ironic dimension to Steve Ballmer's accusation that GNU/Linux was "a cancer that attaches itself in an intellectual property sense to everything it touches". Who is the cancer here? This "support" for "open source" of course comes hard on the heels of co-operation between Apache and Microsoft to support the OOXML file format in Apache's POI project and since Microsoft managed to get OOXML adopted as an ISO standard it tends to leave a bad taste in the mouth. Yes, the good guys lost. Again.

In one leap, from participant to contributor?

If I understand it properly Microsoft will now contribute patches for [PHP[(http://www.php.net/) under an FSF LGPL (lesser GPL) They chose well. The LGPL permits source code to be used with proprietary programs. All the advantages without too many restrictions. Nice.

That recognition perhaps brings us to the kernel (no pun intended) of Microsoft's motives. It has a vested interest in improving interoperability between PHP and Windows as this would help it reduce the drift of PHP to GNU/Linux platforms. Coughing up $100,000 would be a minuscule price to pay for stopping that drift but it is also an admission than Apache has beaten Microsoft's IIS (Internet Information Services). Or perhaps it will only be a Pyrrhic victory of sorts. Microsoft are now free to take Apache source code and proceed to amend, tweak or customise it to the point of what Bruce Perens has called "engineered incompatibility" At that point Microsoft could repeat the successful disaster of bundling Internet Explorer with Windows, only this time it would be Apache and with all the attendant broken web standards that tormented web developers--but this time on the server instead of the desktop.

What's to be done?

Perhaps the time has come for a review of the multiplicity of available licences, if only to protect free software from cynical predators like Microsoft. Safety is not necessarily always in numbers. Sometimes diversity can be as much a weakness as a strength. Ideally GPLv3 should be the role model here. It is the one licence most impervious to these stalking horse tactics and it is no surprise that Gates and Ballmer have always reserved their most vitriolic bile for the GPL. Stallman's seeming obduracy, eccentricity and unswerving take on the "political" nature of proprietary software will prove to be the best protection we can have in such circumstances.

Such misplaced generosity will simply invite Microsoft to pick off the Lamp stack one component at a time. Microsoft certainly "get it". Do Apache?

Perhaps too it is time to reconsider a definition of cross platform that either restricts access by way of tighter licencing along the lines of the GPL or simply abandons making free software available on Windows altogether. I know that one of the ideas driving the cross-platform ethos has been that "information likes to be free" and to let Windows users sample GNU/Linux software on a proprietary operating system in the hope that they will be sufficiently enamoured to make the switch to using that sampled software on a GNU/Linux platform. That's certainly how I made the transition, but how many others do? Besides, reciprocity is, by definition, a two-way street and so far it's all been one-way traffic.

Perhaps the good folk at Apache know what they're doing and can handle Microsoft. Perhaps not. The precautionary principle has damaged the practice of science in the area of public policy but for once I agree with its caution. The Recidivists of Microsoft should not be given the indefinite benefit of the doubt. Such misplaced generosity will simply invite it to pick off the Lamp stack one component at a time. Microsoft certainly "get it". Do Apache?

Category: 

Comments

bugstomper's picture
Submitted by bugstomper on

please correct me if I am wrong but it seems that the problems arise because the Apache licence is not viral and does not support Copyleft [...] This means that programs written under the GPL could not link to other programs whose libraries were GPL-incompatible.

Sorry, but you are wrong here. GPL code can be combined with any code whose license does not add more restrictions to the GPL code. There is no problem linking GPL code with completely unencumbered code, you would just have to follow all of the provisions of the GPL in the combined result. For example, if I take your GPL code and link it with someone else's ASL code, in order to distribute the combination I would have to make all the source code available and allow people to modify it, just the same as if all the code were licensed under GPL. The ASL does not prevent that, so in that respect it is compatible.

The incompatibility with GPLv2 came from a provision of the ASL that provides for protection against a patent attack. If I release code under the ASL I can say that if someone sues me for patent infringement in that code they lose the right to use that code. GPLv2 does not allow for that restriction, which means that ASL would add more restrictions to code it is linked with. GPLv3 deals with that by allowing certain restrictions having to do with patent retaliation.

A good discussion of the details by FSF Europe is at Patents and GPLv3

spartan2276's picture

OK tell me again one more time why do we bother with Free Software if we are going to let Microsoft destroy it, we might as well just quit now since we have all these foundations such as Apache allowing Microsoft to get in there and destroy them from the inside out. Wait and see it will happen, it is currently happening with Novell.

So again why bother with all of it if the community has no backbone, they go and port all of the best software to Windows hoping to change users minds, please if they did not get it back when all this started they won't get it now, because they don't care. What really sucks about all of this is that the LAMP STACK will come to extinction very shortly and there is really nothing anyone can do about it now, call it FUD call it what ever you like unless those folks at the Apache foundation GROW a pair and make sure they stop Microsoft in their tracks KISS it GOOD BYE BABY! The statements made by Steve Ballmer about FOSS being a cancer should be a clear enough message it was for me.

Olle Gladso's picture

I think the prized FOSS software we have should be kept away from Windows and other proprietary OS'es. It galls me when I see people using GIMP on windows and having no idea what FOSS is all about.

iphigenie's picture
Submitted by iphigenie on

I might be naive but I think it is much simpler than that. Microsoft is genuinely interested in projects by the Apache foundation that are *not* the apache web server, and it is not some weird plan to undermine licenses, it is a genuine interest to get these projects realised.

If you look around, the Apache foundations lists about 40 projects. Several of these projects are entreprise level implementations, like lucene, hadoop, synapse etc. Several those have sub projects which are to create a branch of them which is on the .Net platform (most are java originally). Of course it is in MS' interest to support this widening of the Apache foundation projects to .Net.

As I said I could be naive but MS must realise by now that FOSS will not go away, that it might get stronger in tough economic times, and that if there is no open source on their platform they will suffer, especially in the Entreprise level Open Source world.

Author information

Gary Richmond's picture

Biography

A retired but passionate user of free and open source for nearly ten years, novice Python programmer, Ubuntu user, musical wanabee when "playing" piano and guitar. When not torturing musical instruments, rumoured to be translating Vogon poetry into Swahili.