Linux Market Share
In the course of a normal work day I take several little breaks to check the news. On my list of news sites are Slashdot, Linux Journal and Linux Today. Frequently I see something that gives me an idea for an article. Sometimes I even find an article on a topic that I was planning to write about myself. Such was the case today when I came across this well-written piece from the Royal Pingdom Blog referenced on Linux Today. It’s about the failure of desktop Linux to break the 1% market share barrier, and I confess that it left me a little depressed. But I decided to add my two cents on the subject anyhow.
Here’s a chart showing the market share of the major OS distributions over the past year, courtesy of statcounter.com, the same place from which the author got his data:
The Pingdom article suggested that there were several reasons for Linux not having gained greater market share than it has:
- there are too many distributions,
- there are too many GUIs,
- the various Linux desktop products are not polished enough,
- consistency and usability issues exist with the various Linux distros, and
- the various suppliers of Linux distributions focus too much on heavy duty tech-savvy users, and not enough on normal everyday users.
I pretty much agree with all of these points. Except...
I use Windows, and I use Mac OS X. The Windows UI (XP and Vista, more than Windows 7) is notoriously inconsistent. Polished? Not a word I usually use to describe a Windows product.
Mac OSX? It’s UI is certainly different than Windows, and it seems to be more consistent than XP. It’s also less crash-prone. But...
I’d hold my Mint 9 Gnome desktop up against either of those other two in terms of stability, constancy, and that metric which has not yet been mentioned: security. Usability is harder to judge because that is determined more by one’s familiarity with the product than anything else.
Which brings me to my final point: I think the main reason that Linux has not penetrated the desktop market more than it has is because people tend to stick with what they are used to. So, I guess I’ll just have to get used to being depressed, because people are what they are, and learning a new OS is just is not that high on most folks’ “things to do” list.
Practical Task Scheduling Deployment
July 20, 2016 12:00 pm CDT
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.Register Now!
- SUSE LLC's SUSE Manager
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- My +1 Sword of Productivity
- Managing Linux Using Puppet
- Non-Linux FOSS: Caffeine!
- Doing for User Space What We Did for Kernel Space
- SuperTuxKart 0.9.2 Released
- Google's SwiftShader Released
- Parsing an RSS News Feed with a Bash Script
- Rogue Wave Software's Zend Server
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide