Ten key differences between Linux and Windows
Published: 03 Sep 2008 16:04 BST
Before debating the relative merits and shortcomings of Linux and Windows, it helps to understand the real distinctions between them. Jack Wallen has distilled the key differences into one list.
I have been around the Linux community for more than 10 years now. From the very beginning, I have known that there are basic differences between Linux and Windows that will always set them apart. This is not to say one is better than the other; it's just to say that they are fundamentally different.
Many people, looking from the view of one operating system or the other, don't quite get the differences between these two powerhouses. So I decided it might be useful to list 10 of the primary differences between Linux and Windows.
1. Full access vs no access
Having access to the source code is probably the single most significant difference between Linux and Windows. The fact that Linux belongs to the GNU Public License ensures that users (of all sorts) can access (and alter) the code to the very kernel that serves as the foundation of the Linux operating system. You want to peer at the Windows code? Good luck. Unless you are a member of a very select (and elite, to many) group, you will never lay eyes on code making up the Windows operating system.
You can look at this from both sides of the fence. Some say giving the public access to the code opens the operating system (and the software that runs on top of it) to malicious developers who will take advantage of any weakness they find. Others say having full access to the code helps bring about faster improvements and bug fixes to keep those malicious developers from being able to bring the system down.
I have, on occasion, dipped into the code of one Linux application or another, and when all was said and done, was happy with the results. Could I have done that with a closed-source Windows application? No.
2. Licensing freedom vs licensing restrictions
Along with access comes the difference between the licences. I'm sure every IT professional could go on and on about licensing of PC software. But let's just look at the key aspect of the licences (without getting into legalese).
Most corporate higher-ups easily fall victim to the safety net that having a support contract brings
With a Linux GPL-licensed operating system, you are free to modify that software and use and even republish or sell it (so long as you make the code available). Also, with the GPL, you can download a single copy of a Linux distribution (or application) and install it on as many machines as you like. With the Microsoft licence, you can do none of the above. You are bound to the number of licences you purchase, so if you purchase 10 licences, you can legally install that operating system (or application) on only 10 machines.
3. Online peer support vs paid helpdesk support
This is one issue where most companies turn their backs on Linux. But it's really not necessary. With Linux, you have the support of a huge community via forums, online search, and plenty of dedicated websites. And of course, if you feel the need, you can purchase support contracts from some of the bigger Linux companies (Red Hat and Novell, for instance).
However, when you use the peer support inherent in Linux, you do take a chance with time. You could have an issue with something, send out email to a mailing list or post on a forum, and within 10 minutes be flooded with suggestions. Or these suggestions could take hours or days to come in. It seems all up to chance sometimes.
Yet generally speaking, most problems with Linux have been encountered and documented, so the chances are good you'll find your solution fairly quickly.
On the other side of the coin is support for Windows. You can go the same route with Microsoft and depend upon your peers for solutions: there are just as many help sites/lists/forums for Windows as there are for Linux. And you can purchase support from Microsoft itself.
Most corporate higher-ups easily fall victim to the safety net that having a support contract brings. But most higher-ups haven't had to depend up on said support contract. Of the various people I know who have used…














