Background

I think it's impossible to offer a purely objective review on an operating system – qualitative data like the GUI and nebulous concepts like “ease of use” can't be measured. There is a degree of subjectivity in such a review, and I believe it's important to relate that in this article To that extent a bit of background on myself is probably going to be helpful on relating my point-of-view on matters, before jumping into Ubuntu. This section is being written prior to my even touching Ubuntu, so that it doesn't end up reflecting my experience, rather than my expectations.

Based on the computers I have owned and the operating systems I have used, I would best be classified as a Windows user. Like many of our readers (and our editors) I have lived the Microsoft life, starting from DOS and going straight through to Vista. I have clocked far more time on Windows than anything else, and it's fair to say that's where my skills (troubleshooting and otherwise) are strongest.

With that said, I am by no means limited to just a single OS. As was customary for most American schools in the 90s, I had access to the requisite Apple IIs and Macintoshes. But to be frank I didn't care for Mac OS Classic in the slightest – it was a remarkable OS in 1984 and even in 1993 and the age of Windows 3.1, but by the time Windows 95 rolled around it was more of a nuisance to use than anything else. It's through a cruel joke that when starting work in IT in 2001, I was tasked with using the newly released Mac OS X 10.0 “Cheetah” full-time to gauge its status for use on the organization's Macs.

Apple didn't ship Mac OS X as the default OS on their Macs at that time, which should tell you a lot. Nevertheless, while I abhorred Mac OS Classic, Mac OS X was far more bearable. The interface was better than anything else at the time (if not a bit too shiny), application crashes didn't (usually) take out the OS, and the Terminal was a thing of beauty. Sure, Windows has a command line environment, but it didn't compare to the Terminal. Mac OS X was a mess, but there were nuggets to be found if you could force yourself to use it.

I'll save you the history of Mac OS X, and we'll pick up in 2004, where Apple had improved Mac OS X a great deal with the release of 10.3 “Panther.” At this point I was a perfectly happy Mac user for my day job, and I probably would have used one at home too if it wasn't for the hefty price of a Mac and the fact that it would require having an entirely separate computer next to my gaming PC. A bit later in what was probably a bad idea, I convinced Anand to try a Mac based on the ease of use and productivity features. This resulted in A Month With A Mac, and he hasn't left the platform since.

Finally we'll jump to the present day. I'm still primarily a Windows user since I spend more time on my desktop PC, while my laptop is a PowerBook G4. I would rather be a Mac user, but not a lot has changed in terms of things preventing me from being one. To replace my PC with a Mac would require throwing down money on a workstation-class Mac Pro that is overkill for my processing needs, not to mention my wallet.

I also am not a fan of dual-booting. Time booting is time wasted, and while I am generally not concerned about boot times, dual booting a Mac would involve rebooting my desktop far more often than the occasional software installation or security update currently requires. It also brings about such headaches as instant message logging being split in two places, difficulty accessing documents due to file system/format differences, and of course the inability to simultaneously access my games and my Mac applications. In theory I could game from within Mac OS X, but in reality there are few native games and virtual machines like Parallels and the Mac branch of Wine are lacking in features, compatibility, and performance.

I also find the Mac to be a weak multimedia viewing platform. I'll get into this more once we start talking about multimedia viewing under Ubuntu since much of the underlying software is the same, but for now I'll say that libavcodec, the standard building block for virtually all *nix media players, is particularly lacking in H.264 performance because the stable branch is single-threaded.

So while I'm best described as a Windows user, a more realistic description would be a Windows user that wants to be a Mac user, but can't bear to part with Windows' games or media capabilities.

As for my experience with Linux, it is not nearly as comprehensive. The only time I ever touched Linux was in college, where our department labs were Dells running Linux and the shell accounts we used for assignments were running off of a small Linux cluster. I never touched the Red Hat machines beyond quickly firing up Netscape Navigator to check my email; otherwise the rest of my Linux usage was through my shell account, where I already had ample experience with the CLI environment through Mac OS X's terminal.

My expectations for Ubuntu are that it'll be similar to Mac OS X when it comes to CLI matters - and having already seen screenshots of Ubuntu, that the GUI experience will be similar to Windows. I am wondering whether I am going to run into the same problems that I have with Mac OS X today, those being the aforementioned gaming and multimedia issues. I have already decided that I am going to need to dual-boot between Ubuntu and Vista to do everything I want, so the biggest variable here is just how often I'll need to do so.

Index It’s Free - Gratis
Comments Locked

195 Comments

View All Comments

  • ioannis - Wednesday, August 26, 2009 - link

    ...sorry, I think it's Alt+F2 by default. I'm talking about the 'Run Command' dialog.
  • Eeqmcsq - Wednesday, August 26, 2009 - link

    Oh, yes you're right. I stand corrected.
  • sprockkets - Wednesday, August 26, 2009 - link

    Ubuntu doesn't ship with the firewall on eh? Weird. SuSE's is on, and that has been the default for quite some time. GUI management of it is easy too.
  • clarkn0va - Wednesday, August 26, 2009 - link

    For incoming connections I don't quite grasp what good a firewall will do on a system with no internet-facing services. With no open ports you stand little to gain from adding a firewall, and any internet-facing service you might add, well, you don't want to firewall that anyway.

    I can see two theoretically plausible arguments for a host-based firewall, but even these don't really stand up in real-world use: 1) a machine that has open ports out of the box (I'm looking at you, Windows), and 2) for the folks who want to police outgoing connections.

    In the case of the former, why would we open ports and then block them with a firewall, right out of the box? This makes as much sense to me as MS marketing their own antivirus. Third-party firewalls were rightfully introduced to remedy the silly situation of computers listening on networks where they shouldn't be, but the idea of MS producing a host-based firewall instead of just cleaning up their services profile defies common sense.

    In the case of outbound firewalling, I've yet to meet a home user that understood his/her outbound firewall and managed it half-way effectively. Good in theory, usually worse than useless in practice.

    db
  • VaultDweller - Wednesday, August 26, 2009 - link

    Just because a port/service is open, doesn't mean you want it open to the whole world.

    Examples:
    SMB
    NFS
    VNC
    RDP
    SSH
    Web (intranet sites, for example)

    And the list could go on... and on and on and on, really.

    Also, it's erroneous to assume that only 1st party software will want to open ports.

    And that is to say nothing of the possibility of ports being unintentionally opened by rogue software, poorly documented software, naughty admins, or clumsy admins.

    Host-based firewalls help with all of these situations.
  • clarkn0va - Wednesday, August 26, 2009 - link

    Windows firewall doesn't filter by source. In other words, if you want SMB or any other service open to some peers and not others, Windows firewall can't help you; you'll need a more sophisticated product or a hardware firewall for that.

    I'm not saying there's no case for host-based firewalls, I'm just saying it's pointless for most users out of the box, where Ubuntu doesn't need it and Windows should be looking at fixing the problem of unneeded services running, rather than just bolting on another fix.
  • VaultDweller - Wednesday, August 26, 2009 - link

    "I can see two theoretically plausible arguments for a host-based firewall, but even these don't really stand up in real-world use"

    That sounds to me like a claim that there is little or no case for a host-based firewall; at least, that's how I interpreted it.


    "Windows firewall doesn't filter by source. In other words, if you want SMB or any other service open to some peers and not others, Windows firewall can't help you"

    That is incorrect, and you should check your facts before making such statements. The Windows Firewall can filter by source. Any firewall exception that is created can be made to apply to all sources, to the local subnet only, or to a custom list of IPs and subnets.

    The firewall in Vista and Windows 7 goes a step further, as it is location aware. Different ports and services are opened depending on the network you're plugged into, as exemplified by the default behavior of treating all new networks as "Public" (unknown and untrusted) until instructed otherwise.
  • clarkn0va - Wednesday, August 26, 2009 - link

    "The Windows Firewall can filter by source. Any firewall exception that is created can be made to apply to all sources, to the local subnet only, or to a custom list of IPs and subnets. "

    In that case I retract my assertion that an out-of-the-box firewall makes no sense in the case of Windows.

    As for Ubuntu, or any other desktop OS having no open ports by default, I still see including an enabled firewall by default as superfluous. Meanwhile, firewall GUIs exist for those wishing to add them.
  • Paazel - Wednesday, August 26, 2009 - link

    ...not enough pictures. admittedly my interest additionally waned when i read the newest ubuntu isn't be reviewed.
  • philosofool - Wednesday, August 26, 2009 - link

    I'm not done with this article, which I'm loving. However, there's a grammatical/spelling quibble that's driving me nuts: "nevertheless" is one world.

Log in

Don't have an account? Sign up now