Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

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.

I strongly disagree. It is losing exactly the sort of person that the author is: developers who, all else equal, would rather use Linux. But who eventually get tired of the BS and just want something that works and you can actually get software for. I have a lot of sympathy for that.

I write this from a Linux laptop, but that's more out of mulish stubbornness and 15 years of accumulated irritation with Steve Jobs and his dickish business practices.

The last time I got a new laptop I knew I didn't have time to screw around for days with X configuration files. And so I paid a vendor several hundred dollars over list to give me a laptop that JFW. And despite that the sound is still way too quiet. After a few time-boxed 2-hour excursions into whatever sound system they're using this week, I still can't fix it. I've given up.

The only legitimate reason I have for staying on desktop Linux is that I code for Linux servers, and I think it's impossible to really understand system performance if you're not running the same OS. But even that seems shaky to me; hardware keeps getting cheaper and developers keep getting more expensive, so it just doesn't matter as much.

One day some bright Linux spark is going to "innovate" again in a way that I'm expected to put up with their rough edges for 6 months (hello, Unity!) and I'm going to say fuck it and buy a Mac because I just don't have time to screw around right then. Or maybe I'll just want to watch a Netflix movie without hassle, or play the video game my pals are all talking about. And maybe by then it will be a fancy dock for my 8-core Android phone.

Overall, I agree with his point, except that I don't think Linux on the desktop is so much dying as cutting its own throat.



When you write "whatever sound system they're using this week", I know what you mean. There's terrible fragmentation, and buggy libraries get rewritten and replaced by some other buggy thing instead of fixed. That's definitely a pattern. From 2007-9 I even fled to OpenBSD on the desktop to get a more stable OS.

But for the past two and a half years I've used Ubuntu with Xfce, and those problems have become a distant memory. Nothing breaks, nothing gets changed on me (Xfce has moved a few things around, but nothing too terrible). No one forced me to switch to Unity, so I didn't. For me, Linux is more usable and stable than it's ever been. I also seem to see more people running it on the desktop than ever before, and in fact stats from Net Applications show a 50% rise in market share in 2011: http://www.zdnet.com/blog/open-source/is-the-linux-desktop-a...

Inside the Apple-centric echo chamber of HN, it's easy to believe that all the developers have moved to OS X and desktop Linux is dead, but I disagree. Despite its problems, desktop Linux is secure in its (small) niche.


Honestly, I like Unity. Or more accurately, I like where they're going with Unity. And I would like the thing itself if it actually worked reliably. But here I am, running the stock version of the biggest Linux distro on popular hardware, and I have to log out and in or reboot roughly daily.

I don't really believe developers are moving to Apple gear because of HN. I believe it because last time I went on a hiring spree, a lot of people said, "Oh, you're running Linux? Do we have to?"


> I like where they're going with Unity

Fair enough, but why not wait to use it until they get there? Daily reliability problems seem like a lot to put up with just for some cool ideas.

Also, I'm not sure how your interviewing experience supports the conclusion "Linux is dead/dying". What it does seem to suggest is "Linux is unpopular", but that has never not been true (on the desktop).


I'm using it because that's part of the default install. At one point I had the time and inclination to spend futzing with stuff to get it to work, but that's not where I'm at. If something isn't ready to use on a desktop OS, they shouldn't ship it.

My previous interviewing experience wasn't like that say, five years ago.


Then you haven't heard of Xubuntu? It's an alternate flavor of Ubuntu that has Xfce as the default install. Here's an iso that will get you basically the exact setup I have, no futzing required: http://xubuntu.org/getxubuntu/

Already installed stock Ubuntu? Install the xubuntu-desktop metapackage (in Synaptic or 'sudo apt-get install xubuntu-desktop'), log out and select "Xubuntu Session" from the login screen. That's it. I did this on my laptop after realizing I didn't want to switch to Unity. (For bonus points you can remove the Unity desktop apps, but that's hardly necessary unless space is at a premium.)

I don't think I'd put up with Linux myself if it was as much of a pain as you seem to think. For me, Xubuntu has been no trouble at all.


What are you using for sound? I use Pulseaudio on my desktop (custom built with a M-Audio Delta 2496 Pro soundcard) and on my laptop (crappy Lenovo G575) and I don't have any problems at all.

All I do is have this line in my .xinitrc:

   [[ -x /usr/bin/start-pulseaudio-x11 ]] && start-pulseaudio-x11 &
And it works perfectly! If I want to change my volume or manage which device it outputs on, I just run pavucontrol


What distro are you using that you are having to start pulseaudio manually? I swear I thought it was default everywhere.


He might be using Arch or Gentoo, or another of the more "DIY" oriented distros. Last time I used Gentoo you still had to really go out of your way to install pulseaudio, though that was four years ago so I don't know if that has changed.


It's Arch, and it's really rather easy to install PA

  # pacman -S pulseaudio pulseaudio-alsa
And if you're ok with having GConf installed (ugh)

  # pacman -S pavucontrol paprefs


I'm using Arch, but this applies to any distro if you don't use a DM and instead use xinit.

I much much prefer the simplicity of only using what I at least partially understand - the more magic (ie a DM) the more shit to go wrong that you don't understand.


It is the default in all mayor DEs, but he might have a custom X session, using a standalone window manager and extra tools. Or he could work in the console.


Many of the problems people have with Linux have nothing to do with Linux itself.

When I first tried to use Linux about 7 years ago, wireless drivers were a huge problem. Manufacturers didn't provide assistance--not much Linux distros could do about it at the time.

These problems are simply inherent to Linux being a minority platform.


> Many of the problems people have with Linux have nothing to do with Linux itself.

I disagree.

What the OP is complaining about is the same thing Miguel was complaining about, and it's the exact same thing JWZ called out 9 years in his CADT rant[1]. It has nothing whatsoever to do with manufacturers failing to provide drivers and everything to do with attention-deficit devs never wanting to knuckle down and do the hard, unglamorous work of long-term maintenance and bug fixing.

Working systems (with known bugs) are thrown out and re-written as new, incompatible systems with even more bugs. Everything breaks every time some idiot decides that they'll rewrite the audio/desktop inter-op/init/logging/whatever subsystem because This Time It'll Be Done Right™. This perpetual treadmill of half-working betas never ends.

It gets old.

[1]: http://www.jwz.org/doc/cadt.html


OpenBSD actually made a huge contribution here by reverse-engineering binary blobs and writing open-source drivers that could be maintained and debugged, which eventually made their way into Linux. At one time, the wireless support on OpenBSD was vastly superior to Linux. (This is a bit of a tangent, but I think props are due.)


> These problems are simply inherent to Linux being a minority platform.

I suspect part of the reason people spend so much time with advocacy is that popularity does pay off, long term: popular platforms get more support, more applications, and more other people who can help you with your own problems.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: