Brad Wardell's views about technology, politics, religion, world affairs, and all sorts of politically incorrect topics.
Microsoft's view of third parties threatens to drive developers, users to Linux
Published on September 9, 2003 By Draginol In Personal Computing
I'm wearing my Register shirt as I type this so given I'm already apparently a tool of The Register I might as well go all the way and point you to an article John Lettice there has written about Microsoft's seeming obsession with Linux.

Personally I think Linux is crap. At least from a desktop point of view for getting general office productivity done.  But as a server, Microsoft needs to worry. I think they have an uphill climb to win the argument that Windows is less expensive than Linux due to TCO (total cost of ownership) because that is only true while Linux specialists are hard to come by and hence can charge a premium for knowing the arcane ways of Linux.

The real problem with Windows on the server is cost per license combined with scalability. Microsoft has increasingly closed the door on third parties being able to extend Windows.

To use a basketball analogy, it's like when you're playing a 4 on 4 game and your team is losing. There is that temptation, when you think you're the best player on the team, to try to do it all yourself. In the end though you'll lose. I think there's an argument to be made that Microsoft is suffering a bit from that.  Rather than just open the door further and let third parties provide solutions, Microsoft seems paranoid about security in the wrong places.

For instance, a lot of what makes Linux appealing for IT people is its transparency. It's "simple" if not user friendly. Stardock's a Microsoft shop and the difference between doing dynamic pages where you have X.wincustomize.com on IIS versus what you can do on Linux out of the box is just one example of where Microsoft envisions the OS being used in specific ways and tailoring the OS for that. In contrast, Linux, because of its open development structure tends to not have any particular focus which has the good side of making easier to mold to a specific use.

Longhorn, from what we've seen early on, has us concerned because it may be going even further in that direction. Microsoft recently made an announcement saying that nearly half of all Windows crashes were due to non Microsoft code. The inference, to me, was that if only people would stop using crappy third party software Windows would be perfect. Of course, that's absurd. It ignores that there's a lot more third party software being run than Microsoft and yet Microsoft's code seems to cause the majority of the crashes.  But worse, it's the entire attitude that third party software developers are a pain for them.

The security craze is really what's driving things right now over there combined with a concern that Linux is making in roads. Put together, it's creating a mindset, at least from here, in which third parties are really just a potential security issue that they wish would go away. I could be wrong on that but consider this -- Windows XP bundled zip, image management, CD burning, instant messaging, movie making, skinning, and other software which cuts many developers off at the knees.  Longhorn is scheduled to come with a built in database layer on top of NTFS, DVD burning, and virus scanning. And that's with 2 more years at least before release, who knows what they'll add in the meantime.

But it gets worse than just the bundling. In the name of security, there are talks of making much hard to extend the OS. Hooks and other ways third parties use to extend the base feature set of the OS may be taken away to make the OS secure (yea because that's where all those viruses come from! system hooks! Not say Outlook Express email attachments and vulnerabilities in protocols...).  This won't have much affect on companies with the resources (i.e. money) to spend the time to "do it right" (i.e. Stardock) but it'll close the door on freeware and many shareware developers who just don't have the time or knowledge to navigate the maze of security or digital signing licensing or whatever to make innovative new stuff.

Consider this: If Instant Messaging hadn't already been invented and Longhorn came out as currently planned you'd not likely see it because instant messaging relies on a keyboard/mouse hook to determine when a user is at their machine. Now Longhorn is likely to allow such hooks still because of instant messaging but that's just the point, who knows what other things that won't be possible because of this kind of "security".

And as a result, these developers are going to increasingly move to Linux. You can see this already. I know of a few Fortune 100 companies who are moving to Linux on the desktop as well as the server because Linux is easier for them to customize.

Microsoft, in essence, is helping build Linux without realizing it.

So Microsoft fights back using the same tactics they used with OS/2. Except those tactics won't work this time because Microsoft won primarily for 2 reasons: 1) They convinced third parties not to write for OS/2 -- that their better opportunity was with Win32 and 2) They made it cheaper to bundle Windows.  You can't convince third parties to write to Win32 when Microsoft continually cuts them down through bundling or removing their ability to do things with the OS that Microsoft hadn't already thought of. And Windows can't be cheaper than free.

So now they're moving to the total cost of ownership argument which only work as long as Linux remains hard to use (relatively) and the number of people familiar with it remains low.  And Windows is no panacea. I still can't figure out how to get Active Directory to work across domain controllers.

If I were emperor of Microsoft I would be focusing on creating the APIs that open the door to third parties to create the next generation software rather than trying to have it all. I would also suggest trying to develop Windows such that it works more generically. Don't try to envision how it's going to be used all the time and make it difficult to use in ways that MS's team didn't think of.

Just my 2 cents. BTW, I also don't think the security issues in Windows are Microsoft's fault but I'll get to that in my next article.

 


Comments
on Sep 10, 2003
From a architects prospective, I found article you referenced dead on. A good design can be implemented successfully on either a Micosoft platform or a Linux / J2EE platform. I know -- I am in the strange position of designing for both.

For an expense position, it seems ludicrous to argue that Microsoft server-side development is less expensive or as extensible. However, I haven't even seriously considering running Linux on any of my PCs. For this reason, it seems like consumer development will still take place in Microsoft software. In fact, I recently build a VB client application to interface with our J2EE platform, because it was so much easier to take advantage of the Windows native functionality.

But server side, it would be hard to convince me to have to licence a Microsoft toolset for the .NET marketing concept when I can get a more robust toolset (in my view) for significantly less cost.
on Sep 10, 2003
From a architects prospective, I found article you referenced dead on. A good design can be implemented successfully on either a Micosoft platform or a Linux / J2EE platform. I know -- I am in the strange position of designing for both.

For an expense position, it seems ludicrous to argue that Microsoft server-side development is less expensive or as extensible. However, I haven't even seriously considering running Linux on any of my PCs. For this reason, it seems like consumer development will still take place in Microsoft software. In fact, I recently build a VB client application to interface with our J2EE platform, because it was so much easier to take advantage of the Windows native functionality.

But server side, it would be hard to convince me to have to licence a Microsoft toolset for the .NET marketing concept when I can get a more robust toolset (in my view) for significantly less cost.
on Sep 10, 2003
Well, I've been using Linux for 6 years, and I definitely do not think it's crap for the desktop (but don't get me started with WinXP ... your great software helps a bit, but I can't get used to it). However I don't think Linux for the desktop is ready for prime time yet. What I see is the amazing progress that has been going on, so I am fairly optimistic some day, in a couple years, Linux on the desktop will be a reality. And that will be the right time to compare it to Longhorn, too
on Sep 10, 2003
Very interesting from someone knowledable. My experience with linux desktop echoes you sentiments. I spent about 6 months trying to use it and endless hours importing fonts and messing with screen refresh rates... and I got it to look OK, but the death of it was that neither Wine nor any other of the emulators could run a couple programs I simply have to have.

I was so disappointed that Microsoft was not broken up in court, the situation so begged for that to happen. And if not broken up at least forced to release the source code or a generic windows. I was disappointed because I thought that it would have resulted in a flowering of options for average Joe user like me.. and my name happens to be joe : ).
on Sep 12, 2003
I have been using Linux on my desktop for a few months. Mandrake 9.1 was my distro of choice and I will definitely upgrade to Mandrake 9.2 when it gets released. I'm a power user, so I like taking the time to learn how to do the "not so easy" stuff on Linux. Actually installing programs from source is not that hard at all. It is just a hassle since installing a new application is not as simple as double clicking an installer. I now use Linux more than Windows XP because Windows XP is slower and because I don't have to worry to much about keeping up with the latest patches and getting hit by worms in Linux. For a worm to do damage in Linux, you would either have to be logged into your root account using it the same as you would use your user account, or you would have to enter your root password. Without root access, viruses and worms cannot delete an of your system's vital files. Security was definitely a consideration in the beginning of Linux's development while security is only an after thought Windows. If Longhorn is being rebuilt from scratch rather than just being a build based on the NT code, maybe now Microsoft is giving security a major priority in Longhorn development. I doubt I will upgrade to Longhorn. It sounds like to me that Microsoft is trying to limit the ability of third party developers to take full advantage of Longhorn so that only Microsoft brand apps work correctly. I'm going to stick with Linux, but I probably will still use Windows XP once in a while until third party developers move over to Linux and Linux becomes mainstream (if that will happen).
on Sep 17, 2003
This article from the 9/11/03 Economist, reprinted below, gives reasons for Microsoft's seeming paranoia.

Governments like open-source software, but Microsoft does not

IN MAY, the city of Munich decided to oust Microsoft Windows from the 14,000 computers used by local-government employees in favour of Linux, an open-source operating system. Although the contract was worth a modest $35m, Microsoft's chief executive, Steve Ballmer, interrupted his holiday in Switzerland to visit Munich and lobby the mayor. Microsoft even dropped its prices to match Linux—a remarkable feat since Linux is essentially free and users merely purchase support services alongside it. But the software giant still lost. City officials said the decision was a matter of principle: the municipality wanted to control its technological destiny. It did not wish to place the functioning of government in the hands of a commercial vendor with proprietary standards which is accountable to shareholders rather than to citizens.

Worryingly for Microsoft, Munich is not alone in holding that view. Across the globe, governments are turning to open-source software which, unlike proprietary software, allows users to inspect, modify and freely redistribute its underlying programming instructions. Scores of national and state governments have drafted legislation calling for open-source software to be given preferential treatment in procurement. Brazil, for instance, is preparing to recommend that all its government agencies and state enterprises buy open source.

Other countries are funding open-source software initiatives outright. China has been working on a local version of Linux for years, on the grounds of national self-sufficiency, security and to avoid being too dependent on a single foreign supplier. Politicians in India have called on its vast army of programmers to develop open-source products for the same reasons. This month, Japan said it would collaborate with China and South Korea to develop open-source alternatives to Microsoft's software. Japan has already allocated ¥1 billion ($9m) to the project.

Why all the fuss? Modern governments generate a vast number of digital files. From birth certificates and tax returns to criminal DNA records, the documents must be retrievable in perpetuity. So governments are reluctant to store official records in the proprietary formats of commercial-software vendors. This concern will only increase as e-government services, such as filing a tax return or applying for a driving licence online, gain momentum. In Microsoft's case, security flaws in its software, such as those exploited by the recent Blaster and SoBig viruses, are also a cause of increasing concern.

Government purchases of software totalled almost $17 billion globally in 2002, and the figure is expected to grow by about 9% a year for the next five years, according to IDC, a market-research firm (see chart). Microsoft controls a relatively small part of this market, with sales to governments estimated at around $2.8 billion. But it is a crucial market, because when a government opts for a particular technology, the citizens and businesses that deal with it often have to fall into line. (In one notable example, America's defence department adopted the internet protocol as its networking standard, forcing contractors to use it, which in turn created a large market for internet-compliant products.) No wonder Microsoft feels threatened—the marriage of open-source software and government could be its Achilles heel.

Policymakers like open source for many reasons. In theory, the software's transparency increases security because “backdoors” used by hackers can be exposed and programmers can root out bugs from the code. The software can also be tailored to the user's specific needs, and upgrades happen at a pace chosen by the user, not the vendor. The open-source model of openness and collaboration has produced some excellent software that is every bit the equal of commercial, closed-source products. And, of course, there is no risk of being locked in to a single vendor.

That said, open-source is no panacea, and there are many areas where proprietary products are still far superior. Oracle, the world's second-largest software company, need not worry (yet) about governments switching to open-source alternatives to its database software. But Microsoft is vulnerable, because an open-source rival to its Windows operating system exists already, in the form of Linux.

If Microsoft is indeed squeezed out of the government sector by open-source software, three groups stand to benefit: large consultancy firms and systems integrators, such as IBM, which will be called in to devise and install alternative products; firms such as Red Hat or SuSE, which sell Linux-based products and services; and numerous small, local technology firms that can tailor open-source products for governmental users.

As a result, the company has been fighting back. Microsoft and its allies have sought to discredit open-source software, likening its challenge of proprietary ownership to communism and suggesting that its openness makes it insecure and therefore vulnerable to terrorism. The firm also created a controversial slush fund to allow it to offer deep discounts to ensure that it did not lose government sales to Linux on the basis of price. And Microsoft has paid for a series of studies, the latest of which appeared this week, which invariably find that, in specific applications, Windows costs less than Linux.

More strikingly, Microsoft has been imitating the ways of the open-source “community”. Last year, the firm launched a “shared source” initiative that allows certain approved governments and large corporate clients to gain access to most of the Windows software code, though not to modify it. This is intended, in part, to assuage the fears of foreign governments that Windows might contain secret security backdoors. Microsoft has also made available some portions of the source code of Windows CE, which runs on handheld PCs and mobile phones, to enable programmers to tinker with the code. Tellingly, this is a market where the company is a straggler rather than a leader.

Jason Matusow, Microsoft's shared-source manager, says that developing software requires leadership and an understanding of customer needs—both areas where proprietary-software companies excel. As for proposed legislation that would stipulate one type of software over another, it is anti-competitive and could leave users hamstrung with products that are not the best for their specific needs, says Robert Kramer, executive director of the Initiative for Software Choice, a Microsoft-supported lobby group. Microsoft will advance these views next week in Rome, where it is hosting the latest in a series of conferences for government leaders. But the signs are that many of them have already made up their minds.