Because coexistence is not a stable solution for them, it cannot be for us either. We have to assume that Microsoft's long-term aim is to crush our culture and drive us to extinction by whatever combination of technical, economic, legal, and political means they can muster. So, in evaluating the Get the Facts road show, we need to start by asking how it fits into Microsoft's larger strategic plans.
One level is obvious. It seems to me very likely that Microsoft's UK tour is designed as a trial run of themes that they'll take to the U.S. to the extent they look successful. The UK is not a trivial market, of course, but 50% of all IT spending is still in the U.S., so from a Microsoft strategic planner's point of view that's where the main battle is. We can afford to pin some of our hopes on growth in Europe and developing countries and elsewhere, but Microsoft can't — the time horizon on it is too long for a company whose big challenge is to keep beating revenue expectations every quarter in a market where they have 92% share. If they don't beat those expectations every quarter, their stock tanks, the option pyramid collapses, and it's game over.
The Dog That Didn't Bark
So, how does this FUD campaign differ from all other FUD campaigns? Let's start by considering the things Microsoft is not doing in this road show.
1. They seem to have abandoned using the "open source is intellectual-property cancer" argument directly. This follows the advice their own survey group gave them two years ago that this tactic was backfiring badly. Instead they're pushing this line through bought proxies at SCO and elsewhere.
2. They've quit claiming that Microsoft's products are technically superior. Instead, they talk up transition costs.
3. Similarly, innovation, which was every other word out of a Microsoft exec's mouth a year ago, now seems to have quietly exited their vocabulary. It isn't in Huw's report, and it doesn't show up on the Get The Facts page.
4. Finally, we're not seeing the very recent Microsoft line that actually all software is proprietary because it's owned by somebody, so there's no difference between proprietary and open source.
Like the dog that didn't bark in the night-time, these omissions are significant, because Microsoft marketing is thorough and ruthlessly opportunistic. You can bet money that the reason they're not making these arguments is because they tied them on smaller focus groups, or individually with key customers, and they didn't fly.
The New Party Line
Now let's review what Microsoft is doing. Huw gives us five bullet points:
1. Claim that linux isn't free.
2. Pretend that Shared source is the same as Open Source
3. Make a big deal about the migration costs of moving to Linux
4. Use the Forrester report to claim that Linux is insecure
5. Belittle the quality of the toolset available on Linux
I'll take on all of these, but in reverse, saving the most interesting for last. Do I even need to point out that most of the factual claims are blatant lies brought to you by the same people who got caught faking video evidence in their Federal antitrust trial?
Belittling the quality of the toolset available on Linux actually reduces to a TCO (Total Cost of Ownership) argument, because what a poor toolset means to a manager is that he'd have to hire more administrators to cover the same number of machines. I'll have more to say about winning the TCO argument in a bit.
Use the Forrester report to claim that Linux is insecure. Huw didn't give a link to Red Hat's counterargument. It's a good one, and I'll build some recommendations for action on it later on.
Make a big deal about the migration costs of moving to Linux. Beating this one is easy. All you have to point out is that migration costs money once; per-seat Microsoft licensing fees are forever. Unless Linux TCO is substantially greater than Windows TCO, the sooner you switch, the more money you save.
The really interesting and novel lines are Huw's report of arguments 1 and 2: Claim that Linux isn't free and Pretend that Shared Source is the same as Open Source. Though these have been foreshadowed elsewhere, we haven't seen these used as headline arguments before, and they add up to nearly a reversal of the position Microsoft has taken in the past. Whereas Microsoft has before tried to claim that its products and licensing are different from and better than and more innovative than Linux's, now they're reduced to arguing that you should stick with Microsoft because shared source is just the same as open source. Really. Ignore the attack lawyers behind the curtain.
Linux isn't free. Hello? If there is actually anyone still left on the planet who thinks the term free software was a good idea, I hope they're paying attention. Because what Microsoft is doing here is exploiting the old familiar gratis/libre ambiguity of the word free in yet another way. They're setting up for a claim that free software advocates are lying or deluded because Linux has a nonzero TCO. Therefore, goes the implication, you can't really trust them about that other freedom thing, can you?
Semantic warfare — struggles over the meanings of words as proxies for political or market positions — is just like other kinds of warfare; you want to fight it on the other guy's turf, not yours. Every minute we spend arguing with Microsoft flacks about what free means is a win for them and a lose for us.
This is also why we need to attack the shared in their shared source rather than defending the open in our open source. Fortunately this is easy. We can ask why they call it shared source when they're not giving up the right to sue people who share it for IP violations. Are they giving anything away except the opportunity to be hauled into a courtroom the next time you do something that Microsoft thinks is competitive with it?
Taking It To The Streets
Notice how defensive a position Microsoft is in now. Trying to neutralize shared source by equating it with open source implicitly concedes that open source is something customers want. Microsoft has given up a lot of ground here. Make them give more. Hammer them without mercy — but do it in a quiet, reasonable voice and keep control of the terms of argument. Here are some sound bites for open-source advocates to use in response to the Get The Facts campaign:
* Migration only costs money once; higher Windows TCO is forever.
* Shared source is a poison pill.
* Only the Windows boxes get the worms.
The thing not to do is talk abstractions. FSF-style propaganda about freedom or user's rights has its uses occasionally, but it will register on this campaign's target audience of bottom-line-fixated IT managers as irrelevant or nutty. And when you look irrelevant or nutty, you hand Microsoft a victory.
To put the Microsofties really on the spot, it's most effective to phrase your counters as questions, especially when you can use them to whack Microsoft with a combination of issues like TCO and security. Like this:
* How many Linux machines have been zombied by Netsky, Sasser, MyDoom, or similar worms? Do your Windows TCO estimates include administrator time spent cleaning up after these infestations?
* Can you explain why Windows IIS websites are cracked or defaced more often than Apache ones, despite the fact that IIS runs less than a third the number of sites Apache does?
* Is Microsoft willing to add a hold-harmless clause to Shared Source licenses that protects shared-source licensees against being sued by Microsoft for alleged IP violations related to the software? If not, then please explain again how Shared Source is just the same as open source?
What This Campaign Tells Us
We're winning, people. Microsoft has failed to stop us with better software technology or lower prices; they're incapable of the former and their business model wouldn't survive the latter. The SCO lawsuit isn't flattening our uptake curve enough for anyone to notice. The defections are mounting at previously captive customers; good recent examples include the French and Brazilian governments. Microsoft has to be particularly worried about the huge increase in Linux server shipments Gartner reported in 1Q2004; on current trends, we'll pass them not just in shipped units but in dollar volume early next year. They are not merely feeling the pressure, it has passed their pain threshold.
The choice of arguments in the Get The Facts campaign is an obvious circle-the-wagons move to defend Microsoft's base of large corporate customers and governments. In itself, it is unlikely to accomplish much; at best, if they're both lucky and persuasive, it may slow down the rate of defections temporarily. But it's not going to do any better than that, and here's why:
Microsoft's underlying problem is that it employs about 22,000 programmers; the open-source community can easily muster ten times that number. That means the capability gap that has opened up between the open-source codebase and Windows is only going to get worse from Microsoft's point of view, not better. Time, technology, and market forces are not on their side — so, to survive, they're going to have to change the game so that market forces and the open-source advantage in technology become irrelevant.
Future Wars
So what is Microsoft going to do to try to claw back control after the Get The Facts campaign runs out of sufficiently gullible targets? I expect it to involve legal and political shenanigans much bigger and uglier than we've yet seen. We've been expecting an attack using junk patents as weapons for two years, and I think the only thing that has held it off is that a convicted predatory monopolist with 92% market share can't expect to sue a bunch of developers who are giving stuff away for anyone to use without taking a severe drubbing in the court of public opinion.
I don't doubt they'll get desperate enough to do that, though. The emergence of institutions like the Public Patent Foundation and Groklaw gives us weapons of our own, but expect some bruising battles ahead.
Expect Microsoft to ally even more closely with the RIAA and MPAA in making yet another try at hardware-based DRM restrictions — and legislation making them mandatory. The rationale will be to stop piracy and spam, but the real goal will be customer control and a lockout of all unauthorized software. Two previous attempts at this have failed, but the logic of Microsoft's situation is such that they must keep trying.
I also expect a serious effort, backed by several billion dollars in bribe money (oops, excuse me, campaign contributions), to get open-source software outlawed on some kind of theory that it aids terrorists. We can only defeat that by making sure that national governments become so attached to open-source code that their military men and bureaucrats will short-stop the bribed legislators, rather than let their vital infrastructure be outlawed.
Large corporations were the right first target five years ago, because converting some of them was the most efficient way to change the demand patterns perceived by the rest of the computer and software industry. That trend is self-sustaining now; I think we passed the tipping point about six months back, and the Get The Facts campaign is evidence of this.
But in the next year, I think we need to focus more on government adoptions, in order to protect our political and legislative flanks. We need to make the cost of suppressing us higher than the sixty billion dollars Microsoft can afford to pay.
Copyright © 2004 by the Open Source Initiative
Send questions or suggestions about the website to webmaster at opensource.org
Note: Comments are owned by the poster. We are not responsible for their content.
One of the reasons why Microsoft has done so well in the market place is their insistance of supporting legacy applications in their new operating systems. A cost to this has been technical flaws appearing (and sometimes being ported to) Microsoft's Windows product, but the market cost of this has been insignificant to users not having to re-purchase third party applications while "enjoying" the Windows OS latest "features".
However, one thing the Open Source systems has done is to raise expectations as far as reliability and scalability of operating systems, and what with Microsoft's stratergy of DRM'ing as much as possible the backward compatibility component is getting broken.
This is creating an enormouse opportunity for Open Source, and other MS competitors, to knock Microsoft off the number one spot: when people have to upgrade/change their third party software anyway there is less reason to stick with the same OS vendor.
Redmond are well aware of this, so we can expect FUD and marketing behaviour comparible to a fish bouncing and bashing about in the bottom of a boat after being caught.
I consider it part of my responsibility to see it does not bounce back into the water...
case in point, a <A HREF="http://slashdot.org/article.pl?sid=04/06/22/1413221&mode=thread&tid=109&tid=126&tid=128&tid=172&tid=187" title="slashdot.org">slashdot artice regarding SP2 for XP</a slashdot.org> has just appeared....
Tech Republic has an article on <A HREF="http://techrepublic.com.com/5100-6264_11-5222856.html?tag=sc" title="com.com">some of the changes that will be coming with Service Pack 2 for XP.</a com.com>
I've already had one consulting client, a medium-sized business, move to planning a transition to Linux, after they saw how much of their old stuff would not move from Win 98 to XP.
To quote the CEO, "If we're going to have to change a lot of stuff anyway, we should change to something that will be most reliable and least expensive in the long run."
(Oh, and they don't have to buy all new machines.)
Only trouble is that they have put a lot of money into broadband. They really are in a pickle.
Example:
"Make a big deal about the migration costs of moving to Linux. Beating this one is easy. All you have to point out is that migration costs money once; per-seat Microsoft licensing fees are forever. Unless Linux TCO is substantially greater than Windows TCO, the sooner you switch, the more money you save."
This is crap. Ever heard of "interest"? "Cost of money"? Think about it.
As is the parent post.
I was wondering just how long it would take for one of these anti-ESR posts to show up.
``Ever heard of "interest"? "Cost of money"?''
Ever hear of viruses and worms? Those cost money to get rid of. My employer spent just under US$500K last summer ridding the Windows desktop systems and servers of a single infestation. The UNIX and Linux systems I use and manage didn't see a bit of downtime. How much principle would you need to have in the bank to accrue enough interest to cover that little aspect of the TCO associated with running Microsoft software? And remember, you could be hit with that cost several times a year. Tough to budget for, too. And in case you haven't had to do it, it's no fun at all having to go to management to ask for money for things that weren't planned for. (Which is why I've distanced myself from the MS arena as much as possible.)
I completely agree with you. I'm not attacking Linux, or saying that Linux isn't cheaper. I'm attacking ESR's flawed reasoning. As so often happens when someone is deeply convinced about something, ESR uses flawed reasoning to reach correct conclusions. This just provides ammunition for the enemies of free software.
However, blaming the argument on ESR only shows your overall ignorance of the history of Free Software.
Eric,
Good point, however there are a number of factors which mitigate this advantage.
First, a huge number of these programmers are not working on OS full time. Most of them have day jobs which may or may not involve actual development of OS software. People may in fact be extremely creative, and get 2x the development output for an equal number of actual hours worked, but that is still less than full time. I'd make a wild guess at somewhere around 10% to 20% working at somewhere near the same level of output as the average MS programmer. That still leaves you at a significantly higher total output, but not nearly what you might think by simply counting warm bodies.
Second, for what it's worth, Microsoft engineers are working in a coordinated fashion. They have a hierarchy, with high level architects calling the shots, and making sure things work together. OS developers are organized, but it is still a much more add-hoc sort of "meritocracy". You often see several versions of the same thing (e.g., nearly a dozen different Jabber and IM clients last time I checked), where projects often consume a huge amount of resources, and then fizzle out.
Of course, this "coordination" is a two edged sword! When everyone is marching in the same direction, it is very easy to have everyone marching in the wrong direction. If you only have one version project planner software, and there are serious problems with how it works, or you discover that people want to do use a Web client rather than a standalone app, then you are up a creek without a paddle. On the other hand, if there are 12 different Jabber clients, then if the one you are currently using ends up being a dead-end because everyone has moved on to a different platform, then you aren't left holding the bag, and it is possible to switch to something else. Of course, in this scenerio, open standards become a key issue!
So, I think the general development of OS software is moving a lot faster than it is in MS. However, it isn't nearly as much of an advantage as you make it out to be, and there are a lot of dead-ends and lost effort. This doesn't even address the issue of device drivers for proprietary hardware, but hopefully as manufacturers see the change in direction OS is bringing, many of them will start to open up at least the API's to their devices.
When will people wake up?
Posted by: OwlWhacker on June 22, 2004 11:28 PMLook at all of the discarded FUD trailing behind Microsoft, why aren't people getting wise to this and putting all of their efforts into switching away from Microsoft solutions?
Sheesh. Crazy.
#