Language Selection

English French German Italian Portuguese Spanish

10 OSes on the Move

Filed under
OS

It's certainly been quite a decade in the world of enterprise operating systems: There have been some spectacular winners, like Linux, and few epic failures, like Microsoft Vista. With the end of the decade little more than two weeks away, now seems a good time to take a look at what the future might hold. So to mark the end of the Noughties and the start of the Tens — or the Noughties R2, as they probably say at Microsoft — here is a highly subjective list of 10 OSes that will (or in some cases won't) be making the news during the next 10 years.

On the way down:

10: SCO Unix — Are you still here?

Like an infernal zombie from Call of Duty 5, SCO is the company that refuses to die. For most of the decade it's been suing IBM and Novell on the grounds that Linux contains its IP. Back in 2003, this was significant, as it had the potential to undermine enterprise confidence in Linux. Since then, SCO has lost multiple hearings and filed for bankruptcy. Somehow it's still dragging itself along the floor with its tongue, and more legal action is promised in the future. Is there still such a thing as SCO UNIX? Can't remember; moreover, don't care.

9. Novell NetWare — good while it lasted
8. OS X — The Zhu Zhu hamster of OSes
7. Solaris
6. Ubuntu

Rest Here




More in Tux Machines

Android Leftovers

Leftovers: OSS

Ubuntu 16.04 Review: What’s New for Desktop Users

Ubuntu is a tricky distribution. As much as I love it on my home server, my desktop is a different ballgame. In my experience, releases between LTS versions have many new technologies that may or may not survive in the next LTS. There were many technologies or features that Canonical thought were ambitious -- HUD, experimenting with menus, online dash search, Ubuntu Software Center, etc. -- but they were abandoned. So, if I were to use Ubuntu on my desktop, I would still choose LTS. Read more

Workflow and efficiency geek talks Drush and Drupal

I started using Drupal because I needed an open source content management system (CMS) to use in several community projects. One of the projects I was involved with was just getting started and had narrowed its CMS selection down to either Drupal or Joomla. At the time I was using a different framework, but I had considered Drupal in the past and knew that I liked it a lot better than Joomla. I convinced them to go with the new Drupal 6 release and converted all of my other projects for consistency. I started working with Drush because I wanted a unified mechanism to work with local and remote sites. My first major contribution to Drush was site aliases and sql-sync in Drush 3. Read more