Ten key differences between Linux and Windows

Ten key differences between Linux and Windows

Summary: Before debating the relative merits and shortcomings of Linux and Windows, it helps to understand the real distinctions between them.

SHARE:
Before debating the relative merits and shortcomings of Linux and Windows, it helps to understand the real distinctions between them. Here are the key differences distilled 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 licenses. 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 licenses (without getting into legalese).

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 license, you can do none of the above. You are bound to the number of licenses you purchase, so if you purchase 10 licenses, 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...either a Linux paid support contract or a Microsoft paid support contract, I can't say one was more pleased than the other. This raises the question: 'Why do so many say Microsoft support is superior to Linux paid support?'

4. Full vs partial hardware support
One issue that is slowly becoming nonexistent is hardware support. Years ago, if you wanted to install Linux on a machine you had to make sure you hand-picked each piece of hardware or your installation would not work 100 percent. I can remember, back in 1997-ish, trying to figure out why I couldn't get Caldera Linux or Red Hat Linux to see my modem.

After much looking around, I found I was the proud owner of a Winmodem. So I had to go out and purchase a US Robotics external modem because that was the one modem I knew would work.

This is not so much the case now. You can grab a PC (or laptop) and most likely get one or more Linux distributions to install and work nearly 100 percent. But there are still some exceptions; for instance, hibernate/suspend remains a problem with many laptops, although it has come a long way.

With Windows, you know that pretty much every piece of hardware will work with the operating system. Of course, there are times (and I have experienced this over and over) when you will wind up spending much of the day searching for the correct drivers for that piece of hardware you no longer have the install disk for.

But you can go out and buy a cheap Ethernet card and know it will work on your machine (as long as you have, or can find, the drivers).

You also can rest assured that when you purchase that insanely powerful graphics card, you will probably be able to take full advantage of its power.

5. Command line vs no command line
No matter how far the Linux operating system has come and how amazing the desktop environment becomes, the command line will always be an invaluable tool for administration purposes. Nothing will ever replace my favorite text-based editor, ssh, and any given command-line tool. I can't imagine administering a Linux machine without the command line.

But for the end user, this is not necessarily the case. You could use a Linux machine for years and never touch the command line. Same with Windows. You can still use the command line with Windows, but not nearly to the extent as with Linux. And Microsoft tends to obfuscate the command prompt from users. Without going to Run and entering cmd (or command, or whichever it is these days), the user won't even know the command-line tool exists. And if a user does get the Windows command line up and running, how useful is it really?

6. Centralized vs non-centralized application installation
With Linux you have (with nearly every distribution) a centralized location where you can search for, add or remove software. I'm talking about package management systems, such as Synaptic. With Synaptic, you can open up one tool, search for an application (or group of applications), and install that application without having to do any web searching (or purchasing). Windows has nothing like this. With Windows, you must know where to find the software you want to install, download the software (or put the CD into your machine), and run setup.exe or install.exe with a simple double-click. For many years, it was thought that installing applications on Windows was far easier than on Linux. And for many years, that thought was right on target. Not so much now. Installation under Linux is simple, painless and centralized.

7. Flexibility vs rigidity
I always compare Linux (especially the desktop) and Windows to a room where the floor and ceiling are either movable or not. With Linux, you have a room where the floor and ceiling can be raised or lowered, at will, as high or low as you want to make them. With Windows, that floor and ceiling are immovable. You can't go further than Microsoft has deemed it necessary to go. Take, for instance, the desktop. Unless you are willing to pay for and install a third-party application that can alter the desktop appearance, with Windows you are stuck with what Microsoft has declared...is the ideal desktop for you. With Linux, you can pretty much make your desktop look and feel exactly how you want/need. You can have as much or as little on your desktop as you want. From simple flat Fluxbox to a full-blown 3D Compiz experience, the Linux desktop is as flexible an environment as there is on a computer.

8. Fanboys vs corporate types
I wanted to add this because even though Linux has reached well beyond its school-project roots, Linux users can be soapbox-dwelling fanatics who are quick to spout off about why you should be choosing Linux over Windows. I am guilty of this on a daily basis (I try hard to recruit new fanboys/girls), and it's a badge I wear proudly.

Of course, this is seen as less than professional by some. After all, why would something worthy of a corporate environment have or need cheerleaders? Shouldn't the software sell itself?

Because of the open-source nature of Linux, it has to make do without the help of the marketing budgets and deep pockets of Microsoft. With that comes the need for fans to help spread the word. And word of mouth is the best friend of Linux.

Some see the fanaticism as the same college-level hoorah that keeps Linux in the basements for LUG meetings and science projects, but I beg to differ. Another company, thanks to the phenomenon of a simple music player and phone, has fallen into the same fanboy fanaticism, and yet that company's image has not been besmirched because of that fanaticism.

Windows does not have these same fans. Instead, Windows has a league of paper-certified administrators who believe the hype when they hear the misrepresented market-share numbers reassuring them they will be employable until the end of time.

9. Automated vs nonautomated removable media
I remember the days of old when you had to mount your floppy to use it and unmount it to remove it. Well, those times are drawing to a close — though not completely.

One issue that plagues new Linux users is how removable media is used. The idea of having to manually 'mount' a CD drive to access the contents of a CD is completely foreign to new users.

There is a reason this is the way it is. Because Linux has always been a multi-user platform, it was thought that forcing a user to mount a media to use it would keep the user's files from being overwritten by another user. Think about it: on a multi-user system, if everyone had instant access to a disk that had been inserted, what would stop them from deleting or overwriting a file you had just added to the media?

Things have now evolved to the point where Linux subsystems are set up so that you can use a removable device in the same way you use them in Windows, but it's not the norm. And besides, who doesn't want to manually edit the /etc/fstab file?

10. Multilayered run levels vs single-layered run level
I couldn't figure out how best to title this point, so I went with a description. What I'm talking about is Linux's inherent ability to stop at different run levels.

With this, you can work from either the command line (run level 3) or the GUI (run level 5). This can really save your bacon when X Windows is playing up and you need to figure out the problem. You can do this by booting into run level 3, logging in as root, and finding/fixing the problem.

With Windows, you're lucky to get to a command line via safe mode--and then you may or may not have the tools you need to fix the problem. In Linux, even in run level 3, you can still get and install a tool to help you out (hello apt-get install APPLICATION via the command line).

Having different run levels is helpful in another way. Say the machine in question is a web or mail server. You want to give it all the memory you have, so you don't want the machine to boot into run level 5. However, there are times when you do want the GUI for administrative purposes (even though you can fully administer a Linux server from the command line). Because you can run the startx command from the command line at run level 3, you can still start up X Windows and have your GUI as well. With Windows, you are stuck at the Graphical run level unless you hit a serious problem.

Topics: Operating Systems, Linux, Microsoft, Open Source, Software, Windows

Kick off your day with ZDNet's daily email newsletter. It's the freshest tech news and opinion, served hot. Get it.

Talkback

125 comments
Log in or register to join the discussion
  • Support

    The only times I've tried to get support from MS, the incident has always been credited back because they could never solve the issue. Corporate support isn't all it's cracked up to be.
    rpmyers1
    • And, the OEMs to do all of the support. MS only supports retail versions.

      So, for OEMs, it is the same. Linux is free and they have to support it. Windows costs a small fortune, ant they have to support it.
      DonnieBoy
      • MS also supports Windows after service packs.

        NT
        mrlinux
      • This was dev support

        This was costly Enterprise dev support, around $2K an incident.
        rpmyers1
        • How was it that much?

          Did you have someone come to your site?
          Joeman57
  • Shouldn't this be titled

    "Ten key differences between Linux and closed source operating systems"? The points listed here are applicable to more than just Windows.
    ye
    • Re: Shouldn't this be titled

      Not everything; for example

      1) hardware support - not all closed source OS has the same level of hardware support.

      2) Command line vs no command line : Many closed source OS has fully functional command line support.

      3) Multilayered run levels vs single-layered run level :- Single layered run level is property of closed source.

      So I guess the article is more of Linux Vs Windows, than Linux Vs closed source
      mKind
      • Re: Shouldn't this be titled

        >> Single layered run level is property of closed source.

        I meant Single layered run level is not a property of closed source.
        mKind
      • You classify three of ten specific to Windows but...

        ...conclude it's still Linux versus Windows.

        I also have to question the benefit of multilayered run levels. Run levels are nothing more than the background services (and perhaps filesystems mounted) when the system starts up.

        While UNIX supports multiple run levels they're hardly anything to get excited about. Single user mode to install patches. Run level three for CLI only. Run level five for GUI. And that's only Linux.

        One could argue Windows has a primitive run level system with Recovery console, Safe Mode, Safe Mode with Networking, and normal.
        ye
        • All it takes is one

          NT
          jasonp@...
  • RE: Ten key differences between Linux and Windows

    How about identifying ten differences for the average
    user; or does Linux never look beyond the Geek ?
    (Difference #11)
    Heenan73
    • Huh?

      I thought the article was about the differences between 2 OSes not the difference between the users. The author did a great job of covering all the bases, both technical and non. Just for good measure, I had my wife read it. She, who is the most basic user you'll ever meet, had no problem getting the parts that would pertain to her. The technical parts she just said "oh" and drove on. So I guess I just don't get your complaint.
      b.bob
    • I thought it was.

      But I can paraphrase for you as I read it...

      Linux may offer less support, but not much and it will give you more control over the core system to fix problems when they do occur. Windows will offer greater support with less control over the incompatibilities at a cost to you. But for the average user on a pre-installed machine you won't any longer know the difference unless you have a particular application your trying to get to run that for saleability or political reasons (i.e. Direct X, MS SQL, etc.) is sold as platform dependent. In these cases however, Microsoft may still be a better choice.
      Socratesfoot
  • Point by Point

    [b]1. Full access vs no access[/b]

    Sure, having access to source code is better than not having access to source code but this doesn't affect the average Joe at all and it also won't affect 99% of corporate users either. Yes, yes, I'm sure people will be able to bring up anecdotal evidence that they've taken advantage of open source and I wouldn't dream of disputing it, I'm only saying that open source is as useful to most people as the engine hood of their car: sure they can open it but most won't.

    [i]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?[/i]

    Huh? You could have dipped into the code of an open source Windows application and you couldn't have done it with a closed-source Linux application so I'm not sure what this has to do with Windows vs Linux.

    [b]2. Licensing freedom vs licensing restrictions[/b]

    Agreed.

    [b]3. Online peer support vs paid helpdesk support[/b]

    Agreed but: [i]Why do so many say Microsoft support is superior to Linux paid support?[/i]

    Who says this?

    [b]4. Full vs partial hardware support[/b]

    Linux has better support for older hardware, Windows has better support for newer hardware. I'm still pissed that my Creative XFi sits useless while I'm booted into Linux. :(

    [b]5. Command line vs no command line[/b]

    [i]But for the end user, this is not necessarily the case. You could use a Linux machine for years and never touch the command line. Same with Windows.[/i]

    Good, so we agree that this is not an issue for most people.

    [i]And if a user does get the Windows command line up and running, how useful is it really?[/i]

    Wait, I thought we just agreed that the command line in both Windows and Linux is simply not necessary. Funny how suddenly it is!

    Regardless, I totally disagree that the Windows command line is not useful. You've been able to build incredibly powerful scripts with vbscript for many years now and Powershell is a fantastically powerful tool. Finally, things like Perl are available for the Windows command line too.

    [b]6. Centralized vs non-centralized application installation[/b]

    Agreed for end users. For the corporation though, Windows offers excellent centralized application installation tools. I'm sure Linux does too although I've never had cause to research this.

    [b]7. Flexibility vs rigidity[/b]

    This isn't fair. You say that with Windows, you are stuck with the default desktop unless you go third party and then you say that Linux is fantastic because of things like Compiz. Um, you realize that Compiz is "third party" too, right?

    However, one thing I love about Linux is that you have much deeper flexibility than you do with Windows. My MythTV box uses SUSE but instead of KDE/GNOME, I went with fvwm since it uses far fewer resources. My Linux server (an old, tired, "I refuse to die" PC) doesn't have a windows manager installed on it at all. There is a reason why XP and not Vista is the one installed on things like the Asus Eee PC!

    [b]8. Fanboys vs corporate types[/b]

    [i]Instead, Windows has a league of paper-certified administrators who believe the hype when they hear the misrepresented market-share numbers reassuring them they will be employable until the end of time.[/i]

    Wow, I'm glad you don't generalize too much! Nice of you again to dismiss 90%+ of the computer using public. The funny thing is that I bet you that there are numerically more "smart" Windows administrators than there are "smart" Linux administrators. Sure, there are probably more "paper MCSEs" than "paper RHCEs" but that has more to do with the popularity of the OS and less to do with how suitable the OS is for the task at hand.

    [b]9. Automated vs nonautomated removable media[/b]

    [i]Think about it: on a multi-user system, if everyone had instant access to a disk that had been inserted, what would stop them from deleting or overwriting a file you had just added to the media?[/i]

    Now you simply need to explain how Windows, a multi-user system for 15 years, manages to get around this.

    [b]10. Multilayered run levels vs single-layered run level[/b]

    Yup, gotta love the flexibility here.

    -------------------------------------

    I think in the end, Linux wins on flexibility every time and if my post seems down on Linux, it isn't, it is down on those who slam Windows with lies. There is plenty of stuff to slam Windows over so I really don't understand why people need to make stuff up or exaggerate the problems that do exist. I would love to see Linux be "the" OS that is installed on the Dell you just bought from Best Buy. I guess I just look around my life right now and I'm pretty pleased with what I'm able to accomplish with a mix of Vista, Linux, XBox, and Windows Mobile. Isn't that what is important in the end?
    NonZealot
    • Excellent post......

      I think you really showed the author of this blog how to look at things objectively. It is plain to see that the author has a biased and thats his choice, but way to look at things with an open mind. I understand it is the authors opinion blog, but you sure did show how an opinion can be skewed.
      OhTheHumanity
      • Maybe he was considering Vista?

        The introduction of Vista has made it much easier to see the authors claims as legitimate.

        Windows Vista is rigid, expensive, and proprietary, MCSE's are nearly worthless if not obtained in the past year, and the command line is not nearly as integrated into the OS. But the article would seem very biased if you're considering Windows products as a whole, especially with server products; which have more command-line interaction and script-ability then personal editions and client OS's.

        One topic he didn't bring up which I think is more important then slamming the credibility of Cert MS Professionals, is that Windows does seem to choose what features it's users need...basic, home, premium, blueberry, etc. Linux GUI and OS are what they are...my workstation can also be my server. That is a huge difference.
        Socratesfoot
        • I disagree with what you're saying.

          "Windows Vista is rigid, expensive, and proprietary, MCSE's are nearly worthless if not obtained in the past year, and the command line is not nearly as integrated into the OS."

          Let's not mix up the scope here. Vista is a desktop OS while MCSE's are concerned with server/network administration and one cert exam is all that is needed to brush-up on Vista which deep-down is not all that different. As for the command line, it's just as integral to the power user in Vista as in XP, if not more so with additional capabilities and especially PowerShell.

          "Windows does seem to choose what features it's users need...basic, home, premium, blueberry, etc. Linux GUI and OS are what they are...my workstation can also be my server"

          How is Windows (an OS) choosing what features I need? I get what I paid for and choose which of those features I want running. I purchased Ultimate for the MCE and future domain support as well as BitLocker. It's what I wanted not what was chosen for me and if I wanted, I could run Apache and MySQL just as I could in Linux at the same cost. Also, what's the "blueberry" feature of Windows?
          jmiller1978
    • Lies?

      "I think in the end, Linux wins on flexibility every time and
      if my post seems down on Linux, it isn't, it is down on
      those who slam Windows with lies."

      Seems to me you agreed with all the points made, with a
      little clarification. Which of these are now lies?

      "There is plenty of stuff to slam Windows over so I really
      don't understand why people need to make stuff up or
      exaggerate the problems that do exist. "

      Examples in the article?

      "...I'm pretty pleased with what I'm able to accomplish with
      a mix of Vista, Linux, XBox, and Windows Mobile. Isn't that
      what is important in the end?"

      It's important to you. Others have different priorities.

      The article outlines points of difference not superiority.
      Seems to do it well.
      Richard Flude
    • On your point 3

      I have actually heard this. Most of it is the customer relationship skills.
      Joeman57
  • RE: Ten key differences between Linux and Windows

    The differences are very clear. Windows just works.
    Linux doesn't. Windows you download and install
    applications. Linux you have to look at the
    application version, then go to the developer's
    personal website, look for the application link, then
    check the version number, then download the source
    code, then open a command line window and enter a
    series of obfuscated commands to get it to unzip, then
    enter even more complex commands to get it to compile
    and hope that it does compile cleanly, then enter even
    more commands to have the executable file install in
    some random directory, then spend time looking for
    where the file was installed, run it, and hope it
    doesn't segfault or cause a kernel panic.

    With Windows everything is based on a standard, files
    go into standard places on the system. With linux your
    files are scattered all over and untraceable because
    linux does not have a standard. Windows you can be up
    and running in minimal time. Using linux you have to
    spend hours upon hours tweaking the system to get it
    to run.

    More and more people are choosing Windows over linux
    due to the many complications involved of running it.
    Companies already have migration plans in place to get
    away from linux. It tries to be a jack of all trades
    but fails at all of them.
    Loverock Davidson