01.01.09
Microsoft History of Exploiting Free Labour Repeats Itself
Partners you can’t trust
WE have already warned Free software developers who are led to believe that Microsoft is genuinely interested in helping them, rather than exploiting them as usual. Those who are new to this debate are advised to read:
- Is Microsoft Embracing Open Source? Like a Python Embraces a Gazelle
- SDTimes Explains Why Microsoft Wants Open Source
- Quote of the Day: Bradley M. Kuhn (SFLC) on Microsoft
- Microsoft’s Open Source Xenophobia
- Novell Resentment: OSI, Others Begin to Wake Up
- Microsoft’s Aggressive Push to Assimilate FOSS to Microsoft
- Don’t Play Politics and Diplomacy with Microsoft
- Microsoft Open Sores (May Contain Patents)
- Speculation: Who or What is Walli? (Or “How Microsoft Invades FOSS”)
- Not Everyone in the OSI Shows “Respect for Microsoft”
- The Anatomy of Invade-to-Subvert Strategies
- A Wooden Horse Knocks on the Door of the Open Source Initiative City
- Bill Hilf and Microsoft’s ‘Terror Culture’
Microsoft is renowned (or notorious, depending one’s point of view) for only exploiting developers who help Microsoft increase sales, e.g. of Windows. If those developers make some money, then Microsoft copies them and undercuts them through pricing or bundling. But there is another form of exploitation, which a reader sent us a tip about. It’s about what Microsoft calls “getting IBMed.”
The definition of “getting IBMed,” says our reader, is “getting our ‘competitors/partners’ to work for us and getting our ‘partners/competitors’ to pay for it.”
And how nicely it is illustrated in this confidential message from Bill Gates to Steve Ballmer (dated August of 1989). We append the full text at the bottom and we have just made a permanent local copy of the original court exhibit [PDF] from Comes vs. Microsoft (Iowa antitrust). One part of it says:
Windows is still not as nice as the mac and it would be easy to be a lot better. Win 3 goes a long ways but we cant get IBMed on this one.
That’s from Bill Gates. He said that the Mac was better, but they needed IBM to help them reverse this, just like with Sony and Playstation. Two days ago, in the Wall Street Journal, the following article was published:
…in 2001 Sony partnered with Toshiba and IBM to create the so-called Cell processor — a chip so powerful that it would redefine PC-scale power…
[...]
In late 2002, Microsoft approached IBM about making the chip for Microsoft’s rival game console, the (as yet unnamed) Xbox 360. In 2003, IBM’s Adam Bennett showed Microsoft specs for the still-in-development Cell core [...] The result was that Sony’s R&D money was spent creating a component for Microsoft to use against it.
“According to this, Microsoft joined the party late and got IBM to show them the specs for the joint Sony/Toshiba CELL processor [...] only it was Sony that paid for it” says a reader.
The history that we present here is similar and the full text is below. Readers may spot repeated spelling mistakes like “basicly” and “agressive” (it’s not just a typo because it’s repeated separately). Here is a part about patents where Gates says:
First, we have to make sure windows isnt easy to clone for both technical
and legal reasons. Who is smart that thinks about this – patents and
such. I can do it at some point and I think we will be able to achieve ito
DOS being fairly cloned has had a dramatic impact on our pricing for DOS.
I wonder if we would have it around 30-40% higher if it wasnt cloned. I
bet we would!
Another part talks about “software evangelization” (namely “We may need to do some more software evangelization in certain catergories”). By “evangelization”, does he refer to "the Slog"?
Concludes Bill Gates: “IBM never knew our plan and if they did they shouldnt like it – our old plan (DOS) which is the current financial success of the company- sell cheap to IBM and make money from everyone else.” █
Aug 6 21:34 1989 MAIL Page 1
From billg Sun Aug 6 21:34:05 1989
To: steveb
Subject: OS strategy
Date: Sun Aug 6 21:34:03 1989
I have been thinking about this in a pure MS context to understand what
is important for us and then see how the IBM relationship helps with that.
ny worth $7B. Thats
doubling the current valuation. We would have to more than double our
profits. Let say systems has to bear the same proportion of that burden
in the future as it does now and that as a group (server, mouse, lang,
and toolkits) do their share (small) with server making up for the
fact that mouse, lang and tollkits cant bear their part. That leaves
the Os part (dos, win, os/2) with a huge burden. Basicly last year
(I may get the numbers wrong) it was around $180M worldwide PROFIT.
Assuming 12m machines thats $15 PROFIT per machine or giving IBM
1/3 of the market (a little high) $22.5 per non IBM machine. We have to
drive that number up to around $45. Taking a 3 year time frame I think
windows has a lot to do with it -I can see us lowering the price
differential for “high end windows” (a nickname I have for what os/2
has to be perceived as over time) because we want to get it bootstrapped
to the point where it wont cost a lot more than windows does. This means
the price we can charge for windows will drive a lot of our future.
Now how can we get this doubling per system thing to take place.
First, we have to make sure windows isnt easy to clone for both technical
and legal reasons. Who is smart that thinks about this – patents and
such. I can do it at some point and I think we will be able to achieve it.
DOS being fairly cloned has had a dramatic impact on our pricing for DOS.
I wonder if we would have it around 30-40% higher if it wasnt cloned. I
bet we would!
Second, we have to make windows really good – not in the ways we have assig
to os/2 but in ease of use approaches and software environment richness
approaches. We will need smart people to adavnce the product – smaller,
faster for the kernel but smarter for all the interface pieces. Apple
isnt dont what they should in this area and we can. I am not saying to
tilt back towards windows or even to keep particular people but rather to
keep what we have and focus it on refinement of speed/size and interface
stuff. We may need to do some more software evangelization in certain
catergories.
WE have to make windows like DOS is today – basicly new applications all
are done for it and people assume it.
FInancially if we havent tied our hands we need to be able to double the
oem price or go after a VERY agressive retail strategy. The things we
cant afford are:
1. Not being able to improve the product freely. In other words getting
into the mess that Os/2 is in. Windows is still not as nice as the mac
and it would be easy to be a lot better. Win 3 goes a long ways but we
cant get IBMed on this one.
2. A cheap royalty to IBM that means if other oems refuse to per system
license we end up getting very little.
Aug 6 21:34 1989 MAIL Page 2
3. Transferring a lot of money to IBM.
4. Not positioning windows agressively.
If we hold windows back we wont double our oem revenues. I know os/2
is important and we need it to get UNIX apps ported and to fight the
high tech and server battles. But windows is DOS for twice the price
and we need it to be pervasive.
I am afraid of a structure with IBM where we are in partnership for the
following reasons:
a) server businesses arent enough of a gold mine to be a huge part of
our goal. With IBMs cost structure I would like you to explain to me
how a server business can even break even.
b) I am hard core about not putting DOS/win into the financial partnership
If only IBM users buy their package or that % then a low roaylty is ok
but how do we avoid IBM holding us back on windows. Maybe I am paranoid.
c) Lan business is too fast moving to let them write all the code
d) Once os.2 takes over I see our profit per machine actually dropping
and never increasing again. This last point I meant to spend more time
on. Os/2 will dominate eventually and it should allow us at some point
to double again (is that asking too much? maybe) or at least grow per
unit more than the UNIX machines cut into the desktop market so we
grow with the market.
One question I have steve is:
Shouldnt we let the slow pace of negotiation continue? I think that is
in our best interest.
Shouldnt we force them to explain how to make money in the server business
since they are the ones who put so much into it?
IBM never knew our plan and if they did they shouldnt like it – our old
plan (DOS) which is the current financial success of the company- sell
cheap to IBM and make money from everyone else. I prefer an OS.2 deal like
that a lot more than a joint venture. OF course it makes us sensitive to
2 phenomena I worry a lot about: a) cross selling and b) IBM increases
market share. A is the worst since increases in royalties will force some
oems to rely on A. I dont know how to solve that. If you feel we have to
“joint venture” with IBM I think we give up growth opportunity.
SOmehow this discussion is the most important one for the companies busines
future and I guess I should think about it more. In any case there are
some thoughts. You can call them greedy. Its funny but I always thought
other people in the company would end up pushing me to think more about thi
financial upside stuff but it never happens. I was supposed to get to be
a product guy with people pushing me to charge enough but when It comes to
oses I feel more guilty than anyone that we dont have the clear plan to
make 2x as much in oses. Os profit is our past present and future so lets
you and I figure out how to double it without IBM problems. No easy job!
Content is available under CC-BY-SA
Diamond Wakizashi said,
January 1, 2009 at 4:24 pm
Did Ballmer throw a chair at that woman in the picture?
Roy Schestowitz said,
January 1, 2009 at 4:26 pm
No, like most pictures used here, it’s taken from this royalty-free collection.
Jose_X said,
January 1, 2009 at 9:10 pm
This exchange gives the appearance of a clean intro to the real dirty bits discussed later on.
David Gerard said,
January 2, 2009 at 11:10 am
XP is a non-moving target and Wine is doing better and better. MUWAHAHAHA.
Roy Schestowitz said,
January 2, 2009 at 11:15 am
The Novell deal may complicate it somewhat.
Jose_X said,
January 2, 2009 at 4:57 pm
>> XP is a non-moving target
I think it’s a much better target than Vista (much better), but I think wine offers an example that even old API are not what they seem.
[Coders should keep in mind that XP may not be supported in any official way much longer.. perhaps a better related target would be wine itself.]
Microsoft can add things to an installation (in the registry or invisibly) that would be needed in order to properly initialize the system libraries for the application. In some cases, this might be on a per app basis. In other cases, it might be on a per installation basis. The implication would be that applications might need to be hand tuned (reverse engineering) on a case by case basis when ported to any supposed clone of the winapi platform (eg, wine). The good news is that once you would get the app to work, it should continue working.
On XP, during any moment in time when the machine is connected to the Internet (or even without connecting if there are other triggers of dormant code paths) the system library behavior might be changed from right under your nose.
Jose_X said,
January 2, 2009 at 5:20 pm
>> The implication would be that applications might need to be hand tuned (reverse engineering) on a case by case basis when ported to any supposed clone of the winapi platform (eg, wine).
For closed source software, a more accurate statement would be that the clone platform (not the app) would have to be hand-tuned (in undocumented ways) for each app.
I don’t have wine dev experience, btw; however, I expect that whatever tricks XP can pull off, Vista will do in greater quantity and with greater subtlety (at least once Vista gets ironed out).
David Gerard said,
January 3, 2009 at 11:43 am
Wine does support Vista apps as the demand comes up. The way Wine works is, rather than attempting to duplicate the entire sprawling Win32 API, they duplicate parts of it as actual applications turn up that need those bits. Surprisingly little of Win32 is actually used by anyone in practice!
Microsoft frequently uses app-specific workarounds so that badly-behaved old apps will work on new versions of Windows (per Raymond Chen’s excellent blog). So such hacks are actually part of Win32! However, Wine is not indulging in such things until it absolutely has to, or with occasional variant behaviour of DLLs depending which version of Windows it’s set to claim to be.
(I’m not a Wine developer, just a user and fan.)