Arguing the cost of Windows

Here's yet another post where people argue about the cost of switching to Linux: Is Linux Cheaper on the Desktop Than Windows?. The Windows people raise their usual arguments about Linux sysadmins having higher salaries, the Unix/Linux folks counter that you need more Windows admins so those costs aren't true, the cost of viruses is balanced against the supposed virtues of Windows Group Policies scheme, and on it goes.

What most of these people don't know is that we already know the cost difference because years ago we had people switch from Unix to Windows and it ALWAYS cost more. My small Unix customers typically had no sysadmin staff or part time at most. When they switched to Windows, they all ended up with full time support staff - sometimes multiple people.

Is Windows just a lousy OS?

Why? I suppose we could argue that Windows is inherently flawed and all software, whether written by Microsoft or not, is going to have more problems and therefore require more support. We could (perhaps with more justification) argue that viruses are what add to the support costs. That's certainly true, but I can testify that Windows support costs were higher even before viruses became the outrageous mess they are today. As to Windows being more flawed or more difficult for programmers, I don't think we can make a strong case there. Certainly there are weaknesses in design - Windows doesn't handle forks well, for example - but programmers have certainly learned their way around all that. Yet there is the very obvious fact that Windows networks require more support personnel than our old Unix networks did.

That's reality, but the Windows folks still automatically have legitimate counterpoints. They can rightly say that users using dumb terminals simply can't do things that Windows users can - so naturally there would be more support. I'd argue that the terminal users were more efficient and wasted far less time in a day, but let's ignore that and concentrate on the "Windows users do more" part.

I don't think that tells the whole story. The Unix terminal users had just as many needs and desires as Windows users. They always wanted things, but they wanted things that made their work easier. They wanted the computer to "do" things - to reply to emails, to print copies of purchase orders on another printer, to reformat data for them. They asked the programmer, sysadmin or consultant to make these things happen.

And those programmers or support people generally made it happen. They wrote shell scripts, C, Perl, whatever and gave the users what they needed. They could do that because most apps were custom written or at least had available source code or if they didn't they had lots of hooks where you could tie in.

But the Windows stuff didn't. Oh, some Windows apps have API hooks, but I don't think it was (or is) as common or as easy on Windows. I also think that in some places, particularly at smaller networks, the quality of support techs just isn't that good. While I have no statistics to back this up, I think if you polled Windows support techs and Unix techs, asking both if they had decent programming skills, you'd probably find that the Unix techs were more likely to be able to code or at least script solutions to userland issues. That's certainly partly because you HAVE to possess at least a read-only familiarity with shell scripts to get very far at all with Unix or Linux - I don't think the low-level techs in either camp really WANT to learn basic programming skills, but the guys on our side are somewhat forced into it.

Maybe it's just a bad attitude?

I also think that the userland side of Windows encourages a different attitude toward computers. In the days of dumb terminals and even where there were X-Terminals, the computer was the Computer With a Capital C. It was tended to by very special people with esoteric knowledge. An ordinary user wouldn't presume much knowledge of these computer mysteries.

Windows changed all that. Suddenly a lot of things that formerly required the intervention of High Priests could be done right at the user's own keyboard. It's right there, right at the junction of the keyboard and the user's fingers, that a lot of the trouble begins. There are two parts to it. One is the expectation that Windows SHOULD be easy. Terminal users had no such expectations - computers obviously were NOT easy; why else would they need tending by those acolyte priests? In reality, Windows is no more easy or more difficult than our old terminal apps were: users still need training and the quality of the app software itself is most of what causes problems: Windows itself has little to do with it.

Some common ground

The other factor is implied in the words "Windows Operating System". Oh, we had windows, even on character based systems. But the operating system? That's for the guys with long hair, thick glasses and pocket protectors to deal with. Most importantly, there was no importance to the OS at the desktop. If the desktop was a computer at all, it didn't matter very much because its entire expected function was to get at application at the main server. That same model is deployed today with Windows Terminal server and I bet you can find Microsoft citing studies that show how much support cost can be saved in that model.

Let's go look, shall we? You can find Microsoft's case studies at Customer Stories. Searching for "Microsoft Terminal Server" turns up a number of studies praising the cost savings so I think it's fair to say that Microsoft agrees with me this far, at least: thin clients and a central server have a lot going for them. Most of the savings come from desktop support - if the thin client is acting up, you can replace it quickly. If the user is still having trouble, it's back at the server and when you fix it, you've fixed it for everyone. This holds for everything from bad perms to bad viruses and a lot of stuff in between.

So.. if we both have a central server, is it better that the server be Unix/Linux or Windows? Tempting as it is to bring up the virus stuff again now, let's restrain ourselves. Which server will cost less to run and support? We'll pretend that the costs for the OS software patches are equal even though they aren't. We'll pretend that the Linux server needs to have virus protection even though it doesn't. We'll pretend that a Unix/Linux admin actually does cost more per hour even though that's not really true either.. funny how much we have to pretend, isn't it?

Dead Heat?

And after all that pretending, we're probably at a dead heat. I can argue that the Unix/Linux admin can do more and do it faster, but that's opinion and it is going to vary with the skill of the admin. I can cite uptime studies, I can point out that Unix/Linux machines require less horsepower so will either cost less to run or give better performance, but the Windows guys aren't going to just roll over from that.

They aren't going to roll over, period. I think realistically we'd be lucky to drag many of them to a grudging agreement that things are about equal. But hey, that's something, isn't it?

Got something to add? Send me email.

(OLDER) <- More Stuff -> (NEWER)    (NEWEST)   

Printer Friendly Version

-> -> Arguing the cost of Windows


Increase ad revenue 50-250% with Ezoic

More Articles by

Find me on Google+

© Anthony Lawrence

Sat Feb 14 08:29:28 2009: 5411   bob4linux

The TCO of Linux for a simple stand alone desktop user is higher than the TCO of Windows in the same situation without any doubt. Here is why:
I have a colleague in our local computer geeks club in Chiang Mai Thailand who has to support two Windows XP laptops which are used by his wife and daughter in the local school system. When they return home after the days activities this guy does a full virus scan on the hard drives on both computers. He has seven different scan programs and uses a different one each day. Of course he only has one version of the scanners running live for normal use. Each evening he does the scan and does what it takes to remove the malware collection of the day. He has no spare time to waste money going out to a bar or movie theatre. But in such spare time as he has, he sits and frets about what he should do to make his Ubuntu installation on his own computer secure even though he has never been hacked on it. On the other hand I have been exclusively using Linux on my own hardware since the advent of Mandrake 8.3 or so. Over the years I have moved to Debian then Ubuntu. But the point is I get bored of an evening. No virus scans, not even a gui defrag to hypnotise me. So I sometimes go to a movie or a bar, or go visit friends and crack a bottle with them. That costs money! It is far cheaper to stay home and tend a Windows box or two.

Bob Parker

Sat Feb 14 11:23:45 2009: 5412   TonyLawrence

No arguing that :-)

Sun Feb 15 23:02:16 2009: 5433   jtimberman

Clearly there's a lot of time, money and effort in fighting malware on Windows.

However, the fight is taken to the wrong area - the computers.

I have not had a virus or other malware infection on any Windows-based computer I've owned/used in at least 12 years. Why? User education. I educated my wife on the proper use of her internet browser. I educated myself with techniques to reduce the risk of infecting my systems. If the time and money put into antivirus software and malware scans was instead targeted at user education, I think we'd see a lot more efficient users of computers - Windows and otherwise - and a lot fewer issues with infection.

Of course, no one in business wants to actually learn how to properly and safely use their computer. They want to install the widget pack, and go to the seedy video site, and download Mp3's from nefarious sites in Eastern Europe and Asia. And then they wonder why they have virii and adware.

Tue Feb 17 02:17:01 2009: 5447   fbe2

I've never really used Windows much. My first experience in computers was unix on a Sun in the mid 80's, and I've been a *nix person ever since. But, being a resident of the planet Earth, I'm around Windows machines daily, and they invariably crash far more than any of the *nix computers in the lab. I'm told it's the way they deal with memory (don't release it properly) but that's just a rumor I've heard. You can't leave them running without periodic rebooting because of this problem, I think. All I know is that the amount of problems, problems that are very hard to fix because of the MS philosophy of "don't look - don't touch", are frequent, repetitive, an annoying. Most of the time/expert Windows cost in our lab is because it's so damn hard, even for Windows 'experts' to fix problems. And no one but a person who is into pain will ever call Microsoft for help.

We rate Windows problems in units of 'rebooting'. "Hmmm, Joe, this looks like a 25 reboot problem."

Tue Feb 17 02:48:38 2009: 5448   bob4linux

@jtimberman: "Of course, no one in business wants to actually learn how to properly and safely use their computer. They want to install the widget pack, and go to the seedy video site, and download Mp3's from nefarious sites in Eastern Europe and Asia. And then they wonder why they have virii and adware."

Couple of points:
1. While it is true that going to certain sites guarantees infection there have been plenty of instances of legitimate sites being hijacked so if a Windows box never gets infected that is a matter of some luck as well as good management.
2. Virii - that word is the plural of virius. What on earth is a virius?
Vir is the Latin for man and it's plural is viri. So we cannot talk about Windows Viri (Windows Men!)
No such thing, real men use Linux :-)
More seriously, virology is the study of viruses according to my dictionary.

Kerio Samepage

Have you tried Searching this site?

Unix/Linux/Mac OS X support by phone, email or on-site: Support Rates

This is a Unix/Linux resource website. It contains technical articles about Unix, Linux and general computing related subjects, opinion, news, help files, how-to's, tutorials and more.

Contact us

The psychological profiling [of a programmer] is mostly the ability to shift levels of abstraction, from low level to high level. To see something in the small and to see something in the large. (Donald Knuth)

This post tagged: