Baffled Certainties: Betraying Lintel for Wintel
Nov 26, 2003 8:49 AM PT
I've been trying to imagine what the computing universe will look like in late 2008. The exercise not only highlighted the degree to which Linux has become the focal point for anti-Microsoft feeling, but also underscored the risk that the Linux community now faces from commercialization.
In some countries, resentment against Microsoft's pricing, corporate arrogance and shoddy products has become so commingled with anti-Americanism that pricing and functionality are no longer considered important for decision-making. Recently, for example, price cuts and customizations offered in countries as diverse as Thailand and Germany have almost certainly gone well past the level at which their acceptance would have exposed Microsoft to antidumping penalties, but had no effect on the customer's decision to go with Linux.
My belief is, therefore, that Unix -- whether as Linux, BSD or Solaris -- will dominate the desktop everywhere except in the United States by the time 2008 rolls around. The really surprising conclusion, however, is that what will prevent Linux from taking over in the United States is expertise, not the relative price insensitivity of the American market or the absence of anti-Americanism as a sales driver.
Translating MCSE into Linux
Specifically, what I expect to see is that the expertise of the Microsoft Certified Systems Engineers (MCSEs) now responsible for most corporate desktop computing will continue -- meaning that they'll apply what they know from the MS environment to Linux in both server and desktop roles. Mostly, their efforts will fail to produce cost savings or productivity improvements because they'll be using Linux as a substitute for Windows without changing their own behavior or thinking about computing.
Trying to use Linux as a kind of second-rate Windows is like trying to use house cats to pull a dog sled: You get a lot of exercise and frustration, but few positive results. Unfortunately, this has been the story of commercial Unix use for thirty years: A period of growing acceptance is followed by the widespread application of completely inapplicable expertise and consequent implementation disasters, after which the perpetrators quite rightly claim that Unix failed to meet their expectations and scurry back to the technology they know, badmouthing Unix all the way.
Current attempts to perpetuate the client-server architecture with Lintel desktops illustrate this perfectly. In business reality, the typical heavily locked-down business desktop mainly runs applications that individually turn the PC into an expensive, failure-prone terminal to server-based applications and file systems.
Technical Reality vs. Business
Replacing Wintel with Lintel achieves little. Getting rid of the client-server model achieves a lot. By using central servers with smart displays like the new Sunray 1g, the user gets more power and control while the entire Wintel complex -- from help desk to proxy server -- along with all of its weaknesses, failures and costs gets wiped out.
That has enormous positive impacts: Failures stop happening, security becomes a non-issue, all of the help desk and related support staff go away, and user productivity improves markedly. Application support focuses on the application, not the platform, and is delivered by peers who know the job, not bored help-desk people who tell the user to reboot.
That's technical reality. The business reality is that we're not seeing a large-scale shift away from the client-server model. Ask the decision-makers why not, and you'll find it's because the people making the decisions simply don't question the logic of using a 50-million line OS on a 3-GHz desktop PC with 120 GB of disk space to run a client consisting of an unreliable terminal emulator making insecure calls to local libraries.
To them, that's the one and only natural way, while anyone suggesting use of a secure and reliable smart display with a simple 10,000 line OS is both immoral and despicable.
Push them a bit, and they'll generally insist that independent desktop processing protects continuity when the servers go down, but point out to them that servers shouldn't go down, that desktop users can't read e-mail or run Word on documents from unreachable servers, or that the overwhelming majority of Wintel failures take place on the desktop and you may get baffled hostility. But you won't get change.
Does their position make sense? No. Is it expensive for their employers? Extremely. Will it continue? Almost certainly. Why? Fundamentally because they believe they're doing the right thing.
They know that they're doing the right thing because their ideas about deploying technologies were learned through experience and are tried and tested in the Wintel environment. Things like desktop lockdown, server-stored files, storage area networks, DHCP, gateways and proxy servers are the right things in a Wintel environment -- but the wrong things to do with Linux because these are solutions to problems Linux doesn't have.
From a Unix perspective, the Microsoft client-server model looks like something Rube Goldberg might have coughed up during a drug overdose. But to the typical MCSE, this is reality, and so if you make the MCSE use Linux, this is what he'll use it to implement.
He won't do that because he's stupid, incompetent, dishonest or lazy. He'll do it because he's an expert. You've heard the story about the frog and the scorpion? Think scorpion.
Global Linux Growth
Linux growth in Asia and Europe is going to be interesting to watch because of this. Overall, both regions have less MCSE style expertise but stronger hierarchical controls. For most, therefore, the change from Wintel to Lintel will be a change in supplier, not a change in architecture -- undoubtedly why some companies in Europe seem to be exploiting national resentment against Microsoft, against the United States and against the use of English just to power through a change in desktop OS supplier as a short-term means of selling support services for Linux in client-server deployments.
The result, however, should be increasing desktop costs in business and more emphasis on mobile devices -- combination phones, cameras, PDAs and gameboys -- among consumers uninterested in the complexities of home PC use. The Asian situation is differently driven but the forces at work might produce much the same outcome because client-server is client server whether implemented with Wintel or Lintel. The gains come from getting rid of it, not from changing suppliers for it.
In China, a unique combination of paranoia, political information control needs and the drive for national economic independence are behind a focus on government possession and control of the source for any software of significant economic or military importance. That, in turn, makes Linux a natural for countries like Thailand and the Koreas where its adoption lets them keep pace with their oldest enemy -- and biggest trading partner -- while saving a few bucks, forging partnerships with big American firms like Sun, and reducing their World Trade Organization liabilities on intellectual property and other copyright infringements.
Both cases represent important losses for Microsoft while creating commercial opportunities for Linux suppliers. But neither represents either a technical win for Linux or the beginning of a serious revolt against the Wintel client-server model. The likelihood, instead, is that both will lead to the kind of extensive commercialization that becomes a barrier to further technical progress -- dead-ending Linux worldwide just as it enters its prime.
Paul Murphy, a LinuxInsider columnist, wrote and published The Unix Guide to Defenestration. Murphy is a 20-year veteran of the IT consulting industry, specializing in Unix and Unix-related management issues.