Language Selection

English French German Italian Portuguese Spanish

Five ways the Linux desktop shoots itself in the foot

Filed under
Linux

I don't just write about the Linux desktop, I use it every day. At my desk, I tend to use MEPIS and Mint. On the road, it's Ubuntu on my Dell netbook and openSUSE on my Lenovo ThinkPad. I do this because they work well and they're as safe as a desktop operating system can get. So why aren't more people using them?

Microsoft is the biggest reason. Microsoft is a jealous monopoly that doesn't want to share the desktop with anyone. Desktop Linux is just another target in a long list that has included OS/2, DR-DOS, and -- that eternal thorn in their side -- the Mac. It's no surprise, then, to see in the history of the Linux desktop Microsoft has always tried to crush it.

The very first attempt at a mass-market Linux desktop, 1999's Corel Linux Desktop, lasted less than a year. Why? In 2000, Microsoft paid off debt-ridden Corel to kill it.

Much more recently, Microsoft, caught by surprise by the rise of Linux-powered netbooks, brought XP Home back from the dead and offered it to OEMs (original equipment manufacturers) for next to nothing to stem Linux's rise on low-end netbooks.

Okay, it's hard to beat a monopoly that will do whatever it takes to make sure people don't see there's a better, cheaper alternative. I get that. At the same time, Linux has shot itself in the foot quite often. How?

Rest Here




More in Tux Machines

Outsourcing your webapp maintenance to Debian

It turns out that I'm not the only one who thought about this approach, which has been named "debops". The same day that my talk was announced on the DebConf website, someone emailed me saying that he had instituted the exact same rules at his company, which operates a large Django-based web application in the US and Russia. It was pretty impressive to read about a real business coming to the same conclusions and using the same approach (i.e. system libraries, deployment packages) as Libravatar. Regardless of this though, I think there is a class of applications that are particularly well-suited for the approach we've just described. If a web application is not your full-time job and you want to minimize the amount of work required to keep it running, then it's a good investment to restrict your options and leverage the work of the Debian community to simplify your maintenance burden. The second criterion I would look at is framework maturity. Given the 2-3 year release cycle of stable distributions, this approach is more likely to work with a mature framework like Django. After all, you probably wouldn't compile Apache from source, but until recently building Node.js from source was the preferred option as it was changing so quickly. While it goes against conventional wisdom, relying on system libraries is a sustainable approach you should at least consider in your next project. After all, there is a real cost in bundling and keeping up with external dependencies. Read more

How Intel HD Graphics On Linux Compare To Open-Source AMD/NVIDIA Drivers With Steam On Linux

As earlier this week I did a 20-way AMD Radeon open-source comparison, looked at the most energy efficient Radeon GPUs for Linux gaming, and then yesterday provided a look at the fastest NVIDIA GPUs for open-source gaming with Nouveau, in this article is a culmination of all the open-source graphics tests this week while seeing how Intel Haswell HD Graphics fall into the mix against the open-source Radeon R600/RadeonSI and Nouveau NV50/NVC0 graphics drivers. Read more

Leftovers: Gaming

today's howtos