Language Selection

English French German Italian Portuguese Spanish

Desktop Linux: Ready for the mainstream

Filed under
Linux

It's been a decade since Linux proponents first argued their OS was ready for mainstream adoption. Yet for all intents and purposes, Linux remains nonexistent on "regular" people's desks. Sure, developers and other tech experts use Linux, but that's about it.

So when my colleague Neil McAllister, author of InfoWorld's Fatal Exception blog, made the case for desktop Linux, I snorted, "Give me a break! Desktop Linux is nowhere." He challenged me to try it myself. He had a point: It had been a decade since I fired up any desktop Linux distro. So I accepted his challenge.

My verdict: Desktop Linux is a great choice for many regular Joes with basic computer needs. And not just on netbooks.

In fact, I found that it makes a lot of sense to standardize office workers on desktop Linux. I now understand why governments in Asia and Europe say they want to get off the Microsoft train and shift to Linux. I thought these were empty threats meant to get better licensing deals or to blunt some of Microsoft's monopolistic power, but as it turns out, desktop Linux is a worthwhile option for both public organizations and private companies.

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