Live data from Hacker News

What killed the Linux desktop

tirania.org

1–10 of 385 posts

Re: What killed the Linux desktop

#2
Arguing about the niceties of the UI is all well and good but the actually problem is far more fundamental.

What killed the linux desktop? Drivers. Mostly graphics drivers but some others as well. Who cares if the UI isn't ideal if the damn thing can't sleep and wake up properly, or if it spazs out every time I plug in an external monitor.

Re: What killed the Linux desktop

#4
I think some of this is perceptive. It's true that the attempt by both Canonical (Unity) and Red Hat (Gnome 3) to sort-of-incompatibly break away from the so close to standard that it hurts to type this Gnome 2 environment did a lot more harm than good, at least as far as platform adoption goes.

And clearly OS X is an extremely polished Unix and is going to appeal to the more UI-focused of the hacker set. And Miquel is definitely among the most UI-focused of the hacker set. He's also an inconsolate "platform fan". Much of his early work was chasing Microsoft products and technologies, of course; now he's an iPhone nut apparently, and that doesn't really surprise me.

But at the same time the Linux desktop was never really in the game. I use it (Gnome 3 currently) and prefer it. Lots of others do. For many, it really does just work better. But in a world where super-polished products are the norm, a hacker-focused suite of software isn't ever going to amount to more than a curiosity. (And again, I say this as someone who will likely never work in a Windows or OS X desktop.)

So in that light, I think the idea that the Linux desktop got "killed" is sort of missing the point. It's no more moribund now than it was before. It's more fractured in a sense, as the "Gnome" side of the previous desktop war has split into 3+ camps (Unity, Gnome 3 and Gnome2/Xfce, though there are other spliter camps like Mint/Cinnamon too). But it's here and it works, and it's not going anywhere. Try it!

Re: What killed the Linux desktop

#5
Speaking as someone running a Linux desktop (and am writing this on one) there's not much to say other than I agree. I run linux because work gave me a PC and there's no way I can write software on Windows. Of course we all have servers managed off in the corporate cloud somewhere that run ssh/vnc etc, but there's no way I wanted to install putty again or miss out on the unix commands that make (work) life more enjoyable, so I installed Linux, because I write server software, and client sometimes, but browsers make the operating system moot pretty much. There's more variation between browsers than between operating systems - mobile aside. And when I need to try something on Wintel I spin up a cloud instance and use vnc.

When i'm not on Linux I run OSX everywhere else (and IOS) because its unix-like (is) and because it works so well. I am sure Windows 7 and 8 are great, but I doubt they have gotten rid of c: or \ as path delimiter or any of the other nonsense that DOS introduced (copied from PIP) back in the dark ages. why should they, MSFT still runs DOS apps so they aren't going to change and choosing between OSX and Linux on a non-work desktop is a no-brainer, Netflix, Photoshop etc etc etc...

Re: What killed the Linux desktop

#6
> (b) incompatibility across Linux distributions.

This is completely missing the point - a statically compiled end-user binary should be compatible across all distributions of Linux, using the same version of the kernel or any newer version.

The only caveats to that are (a) hardware and (b) poorly-packaged software.

(A) is the fault of hardware manufacturers and is increasingly not an issue these days anyway; driver issues are becoming increasingly rare.

(B) is easy to solve for any open-source software, as it is the responsibility of the community for that distribution to provide the appropriate packaging. They prefer to do it themselves. And they're good at it - it gets done!

If you want to ship a closed-source binary on Linux, just make sure you don't dynamically link it against any libraries that you don't also ship with the binary. Problem solved.

Honestly, I can't remember one single instance ever where I have run into end-user software that will run on one distribution of Linux and not another, as long as that principle was followed.

Re: What killed the Linux desktop

#8
There's room for many approaches, of course. While the perfectionism (or is it lack of pragmatism?) of Linux and its developers may well have held back its wider adoption on the desktop, there's a lot to be said for the its development community's single-minded pursuit of quality and correctness.

As well as Linux's presence in the data centre, witness the success of 'embedded' Linux: many TVs, routers, set top boxes and other bits of sealed-box electronics all run on it. It's broad in its scope because of the large team of divergent interests working on it, and it's able to support those systems because it's been well made as a direct result of that team's philosophy. Is it really so bad that the average Facebooker does't want to use it?

It really is very, very hard indeed to be all things to all men and no single system around today can make that claim. Linux has its place in the world of computing, just like Android, Windows, OSX and everything else.

Re: What killed the Linux desktop

#9
I've used Linux for years and have never had these problems. I think the issue is that getting everything working requires a deep understanding of each component and the system as a whole. If you just follow advice on forums, you will make things worse because you're doing things you don't understand to a system that you don't understand. That's not going to lead to success. You need to be able to think critically about what's wrong and what needs to change, and then execute those changes. No, that's probably not worth doing if you already like Windows or OS X. If you don't, though...

(And, there are of course Linux-based systems that were built by someone controlling the whole experience, and those work really well. Android and ChromeOS come to mind, though those aren't really desktops per se.)

The other day, someone here was complaining about udev. It has ruined Linux forever, or something. I have a different experience: udev has made my life very easy. I have a rule for each device I care about, and that device is automatically made available at a fixed location when it is plugged in. For example, I have a rule that detects a microcontroller that is waiting to be programmed with avrdude in avr109 mode that symlinks the raw device (/dev/ttyUSB) to /dev/avr109. I then have a script that waits for inotify to detect the symlink, and then call avrdude to program the microcontroller. A few lines of shell scripting (actually, it's in my Makefile), and I can just plug in a microcontroller, press the programming button on it, and everything just works. No screwing around with figuring out which device address it's assigned to. How do you do that in Windows?

Re: What killed the Linux desktop

#10
post #2

Arguing about the niceties of the UI is all well and good but the actually problem is far more fundamental. What killed the linux desktop? Drivers. Mostly graphics drivers but some others as well. Who cares if the UI isn't ideal if the damn thing can't sleep and wake up properly, or if it spazs out every time I plug in an external monitor.

absolutely agree. I love linux, its a great os but drivers are a nightmare, honestly, I've never had any linux distro, where I could comfortably buy an IO device and not have to worry about compatability issues. This to me is the biggest problem by far with the os(s) in their current state.
Post reply on HN