How Apple Killed the Linux Desktop
An anonymous reader writes "Klint Finley discusses Miguel de Icaza's thoughts on how OS X killed Linux on the desktop: 'de Icaza says the desktop wars were already lost to OS X by the time the latest shakeups started happening. And he thinks the real reason Linux lost is that developers started defecting to OS X because the developers behind the toolkits used to build graphical Linux applications didn’t do a good enough job ensuring backward compatibility between different versions of their APIs. "For many years, we broke people’s code," he says. "OS X did a much better job of ensuring backward compatibility."' This, he says, led developers to use OS X as a desktop for server programming. It didn't help that development was 'shifting to the web,' with the need for native applications on the decline."
Because nothing beats Linux for package management. Miss not having a repo of open source at my disposal; the App Store will never touch it.
body massage!
Linux killed Linux on the Desktop. "I would be on the Desktop, if it wasn't for those pesky Operating Systems with their fancy backward compatibility!"
Sheesh not another fucktard slashdot troll if we say it enough times it must be true post.
When did slashdot get so fucked up?
Posted from my perfectly working LINUX Desktop thank you very much.
bleat bleat linux must be dead OSX, bleat bleat Linux destroyed by Windows 8, bleat bleat APIs will eat you babies and Linux, bleat bleat TUX is a stoopid logo, Apples are better, Linux must be dead bleat bleat.
Windows 7 was the nail in the coffin, if Windows 7 wasn't as good as it is, and another Vista stinker was pooped out of Redmond then Linux possibly may have had a chance.
I can't manage to notice that Ubuntu or Mageia or Fedora stopped shipping because bam, Linux Desktop is killed by MacOS X. Can you tell us why exactly is Linux dead? (And why would we trust Icasa anyway? It's not like he actually did anything of note or made the right choices in the last 4 years or so.)
So, the way I see it, there are 3 competing families of OSs. That is Windows, Linux and Apple. With Linux traditionally installed on about 1% of desktops, I would think that Windows is the big loser here. If OS X is nowadays installed on 6 -7% of desktops (see: TFA), then it's Windows that lost marketshare.
Sure, it could have been Linux to steal that marketshare. Linux might still benefit from it though... once the market realizes that you can switch without turning your PC into a smoking pile of rubble, they also might try Linux. I still think that Ubuntu is a very decent option.
Gnome3 has killed the Linux Desktop. Thanks.
I agree with the statement that "OS X killed Linux on the desktop", but it's not because Linux developers "defected" to using Mac OS X instead.
Rather, I think it's quite the opposite that actually happened. Designers (not developers!) infatuated with the Mac OS X ideology tried to bring that mindset over to Linux desktop environment projects like GNOME, Unity, and to a lesser extent KDE. Even other applications, like Firefox and Chrome, have been stricken by this problem.
Basically, these designers have done everything in their power to dumb down and otherwise molest the Linux desktop experience. GNOME 3 is the ultimate example of this. While GNOME 2 wasn't perfect by any means (and no software ever is), at least it was usable and predictable. People could use it to get some real work done. Then GNOME 3 came along. It was quickly co-opted and infused with the crap that's commonplace within the Mac OS X and iOS way of doing things.
Anyone who has tried to seriously use GNOME 3 knows what I'm talking about. Put politely, it's a heaping pile of shit. Usability was completely thrown out the window. The emphasis was put on making it look "pretty" and "trendy", rather than making it into a useful tool. This is, of course, a big reason why it fell flat on its face. It's now going down in history as one of the biggest open source disasters of all time.
The same has happened to the Firefox UI. It was once sensible, with the traditional menus and toolbars, and a useful status bar. Then Mac OS X started to become popular among the design community, and things went to hell within Firefox's UI. Like with GNOME 3, usability was again thrown out the window in the name of "aesthetics". Now Firefox's UI is quite awful, and requires much reconfiguration and the use of numerous plugins to restore the usability that the Mac OS X-inspired designers decided to throw out for no good reason.
The Mac OS X and iOS mentality has its place, and that's in low-end (although perhaps unnecessarily expensive), consumer-grade devices meant mainly for consuming pointless social media "content". It does not belong on Linux workstations, especially ones where usability is extremely important, and productivity is a must. But now that it has infected what were once usable desktop environments, many within the Linux community are beginning to really feel the pain of this terrible design ideology.
Like many other geeks I think I looked at Linux desktops back in the Gnome 1 days and thought "Hey, this thing will be really nice in a couple of years when it's finished." Fast forward a coupe of years, a lot of infighting and a rewrite later and I was still thinking that or would have I hadn't lost all faith that these guys could ever produce anything to rival commercial GUI's. So now I'm a mac user and I get all that UNIX-y goodness and none of the open source drama queen bullshit.
If all else fails, immortality can always be assured by spectacular error.
It didn't help that development was 'shifting to the web,' with the need for native applications on the decline.
Yes, it did help. Web applications definately make switching easier (to Mac or to Linux). He's wrong about the web emphasis hurting Linux.
I'm also not sold on the idea that it was backward compatibility that was the problem either. Of all the options, Microsoft has the OS with the best backward compatibility.
First, Mac's consistently break things with each new version, unlike de Icaza states. However, what is brilliant about Apple is every time before they introduce a new feature or break an old feature they have a huge marketing push for it. That marketing push makes the users become interested in that new feature. The developers, who want more users and who may also themselves be excited about the feature, then implement it. This is why we see apps bragging about their Retina graphics on the App Store before Retina machines are even widespread or their notifications or, back in the day, their dashboard widgets. Mountain Lion broke lots. Lion broke lots, but the Mac developers always fix this fast because they are very aware of new software versions due to marketing efforts. Linux has nobody marketing each new feature and edition and focusing both the users and developers in this way.
Secondly, Linux is too difficult for non-computer-literate users to use. It doesn't have to be and indeed strides have been made, but until you will literally never have to use the terminal and you can put a Windows software disk into your Linux CD-ROM drive (while those still exist) and have it install and automatically use Wine with the correct settings and work on the first try without tweaks, it is too hard for grandma.
That said, Ubuntu with Cairo-Dock is a dream to run compared to any version of Windows out there and I have no idea why people don't use it more. I love it. It's not my main OS though. That would be OS X. I'm one of those people using OS X as a desktop for programming that de Icaza talks about, but I can tell you it wasn't backward-compatibility that made me choose it.
Big apple, new Yorik, undig it, something's unrotting in Edenmark.
Refurbished Pentium 4's are a terrible pair of rose tinted glasses to view your computing through. Basing that on your computational future isn't in a good boundary layer.
While lightweight OSs have a place - its not a be all and end all. New computer equipment is in relative terms cheap.
As for Linux, Miguel is right. A sea of shifting APIs might be accepted at the edge, but anyone making stuff needs stability and this is what you get on a Windows or OSX platform - to some degree. Its never total.
Is linux still arguing over the 20 ways to do sound? Still? In 2012?
Good luck to the steam guys trying to build on this sea of swirling open source maelstrom :)
We`re all equal
OS X had already killed Linux on the desktop when Ubuntu didn't even exist yet.
It's a catch-22. Commercial software firms won't write consumer products for Linux because there isn't enough demand. There isn't enough demand for Linux because it doesn't run much commercial software.
I promise I'm not trolling. I was very pro Linux as cool new UIs like Enlightenment started coming out. Shortly thereafter OS X really started taking off (albeit fueled by cool hardware design too) and I found that where the Linux UIs were rough and undependable the OS X UI (+look and feel) was sleek, smooth and very polished. On top of that you had all the functionality of the Linux OS underneath it. Aside from a higher cost, it couldn't compete. Temper this with the fact that I'm focusing on client use and not as much on server use.
Where I see the real value of Linux (and Android) is in embedded systems where GUI design may not be as critical.
-Xen
So your complaint is that you don't know x11 messaging and dbus?
Change is certain; progress is not obligatory.
For the average user, not the technical wizz-kid: the average user, Linux was never an option. Id didn't come on their store-bought PC. If didn't "just work" (ever!) and it didn't support most of the peripherals or USB devices that they had or wanted. Blaming Linux's failure to penetrate the average household on anything but it's own lack of marketing, polish, self-discipline, ease of use, support, brand (i.e. not having a million different distros: all the same, but different) or integration is simply an exercise in self-deception.
OS-X is what Linux could have been if it hadn't fragmented, if it had been properly packaged and supported, if the developers had put some emphasis on ease-of-use instead of "cool features" and obscure options and if it had worked with all the printers, cameras, phones, webcams and scanners that the average user just wants to plug in and have work - immediately and fully.
If Linux teaches us anything, it's that users will pick integration, polish and design over "free" any day of the week.
politicians are like babies' nappies: they should both be changed regularly and for the same reasons
So if I'm reading this right, the way Apple "killed" Linux on the desktop is by offering a quality product, with backward compatability, on solid hardware with just enough *nix plumbing to make most casual shell hackers happy?
Those bastards!
Don't they know that, given enough time, the Linux folks could have offered a similar desktop experience if they wanted to but it was more important to create dozens of competing distributions with slight incompatibilities and sublte differences between them for no earthly reason other than the whims of the distribution packagers.
Ken
In the 1990s, I wanted to get into developing GUI apps for Linux. The single biggest reason why I gave up on it was that the Linux GUI effort fractured into KDE and Gnome camps.
At the time, I figured that one of the two would win out over the other. There was no telling which might win, and I was reluctant to back what might be the losing horse. This was a serious demotivator. Of course, 15 years later, we've ended up with the worst of both worlds: many Linux installations take up the disk space for both, and we've got two unharmonized APIs continuing to fight for a following.
With MacOS, there is no question what API you should use. Apple offers a very clear path. For that reason, I feel more confident developing for that platform.
Comment removed based on user account deletion
Writing this from a Linux desktop at work (yeah yeah) and doing web development. One company forced me to use a AirBook for it and my got is sucked. Not only was it a very badly designed piece of hardware (rounded soft corners EVERYWHERE EXCEPT where you rest your palms. BRILLIANT! I found it to be a slow piece of crap that couldn't be outfitted with a decent amount of memory, something even AMD netbooks can handle (8GB) and the fucking lack of any kind (even MS half-assed version is better) of focus follows mouse makes development just that much more involved.
And those who claim macports is a replacement for aptitude need to have head re-examined.
Yes, a Macbook runs smoother then Windows, then again, what doesn't? But as a replacement for doing webdevelopment for software that will run on Linux servers? Not even close. Especially for the price. Sorry but I don't need USB3. I need a VERY fast SSD, plenty of memory and LOTS of screen space. Lighted keys? I can actually afford ceiling lights thank you very much.
Wait a minute, that name in the summary. Isn't that the mono retard? The thing that has now been completely dumped? Why should I take anyone who thought mono was a good idea serious?
MMO Quests are like orgasms:
You may solo them, I prefer them in a group.
OS-X is what Linux could have been if it hadn't fragmented, if it had been properly packaged and supported, if the developers had put some emphasis on ease-of-use instead of "cool features" and obscure options and if it had worked with all the printers, cameras, phones, webcams and scanners that the average user just wants to plug in and have work - immediately and fully.
If Linux teaches us anything, it's that users will pick integration, polish and design over "free" any day of the week.
This is the most concise statement of the problem I have seen to date. Slashdotters deride the Apple way: 1 choice, hardware and software and it just works. Also the Microsoft way: 1 choice in software, many in hardware and it mostly just works. Then there is the Linux desktop way: many software options all about 80% complete, any hardware as long as you can write your own drivers and kernel modules. The total amount of effort represented by all the Linux options is more than enough to have completed several options fully equivalent to OSX if that effort had been focused into several efforts instead of being fragmented into dozens. Why does the fragmentation occur? Because too much of the rewards for an OSS project (feel-good stuff like having fun, seeing your own name on a project) come from the first 10% of the work. Something needs to encourage people to complete the next 90%: the hard parts like actually making everything work right, accommodating all the variety in machines and peripherals. Then there is the next 1800% of the job: maintenance. These are the weak links in OSS.
Projects that work, such as the kernel and Python, have a single person who maintains the vision. This person is able to enlist the help of others to implement the vision. Notice that both of these traits parallel commercial startups. Worker bees in commercial startups are rewarded with wages and stock. What are the rewards for worker bees in OSS projects?
Bent, folded, spindled, and mutilated.
So your complaint is that you don't know x11 messaging and dbus?
ahh, that's a fatal mistake to mention d-bus where i can hear it being said :) i'll deal with this first, then answer your question directly, ok?
back in 2005 i did a comparison of the d-bus specification and the DCE/RPC specification. the similarity was... unbelievable. i mean, truly, truly unbelievable. the people who wrote the d-bus specification could *literally* have taken the DCE/RPC specification, substituted different words and then published it as the d-bus specification. let me reiterate that, for emphasis, in a different way. *every* concept that is in d-bus is in DCE/RPC.
however, what d-bus does *not* have is the higher-level APIs. d-bus is so immature when you compare it to DCE/RPC (and then to DCOM which is built on top of DCE/RPC) that it is a child's toy by comparison. the main thing that d-bus is missing - the main benefit which you get from DCE/RPC and DCOM - is the IDL compiler.
d-bus expects you to hand-marshal all the data! you get a whole bunch of macros, and you're expected to make your own messages out of them! that's just so fucking shit! you'd actually be better off ripping out d-bus from every single application that has that piece of shit in it, and replacing it with 1500 lines of c code, implementing a unix domain socket, and a bunch of #ifdef macros e.g the SIVAL and SSVAL ones from samba's smb.h header file!
why is that?
because d-bus gives you the *expectation* that it's solving a problem, when in fact it's doing nothing of the sort. at least 1500 lines of c code and a few macros leaves you under no illusions that you still have a hell of a lot of work to do. .... which finally provides some context which allows me to answer your question. d-bus DOES NOT provide a means to make it easy to do backwards-compatible interfaces. it doesn't even make it easy to make *one* interface, so of *course* developers go and change the API and throw out all backwards-compatibility.
what i'm saying is: you've entirely missed the point of what miguel is getting at, and what i am also emphasising. perhaps this is due to a lack of concrete examples. so let's make one, ok?
what do you imagine would happen if you took some component - say... a gnome "clock" widget that plugs into the taskbar - and by that i mean you took the *binary* not the source code - from Gnome 1.0 (whenever it was written - when was it - 15 years ago, now?) and tried to use it in Gnome 3.0?
what would happen? it would utterly, utterly fail, wouldn't it?
now, what miguel's pointing out is that even if you took code from *six months ago*, you have the same problem! and that the consequences of this, over the 15+ years in which linux desktop software has been developing - have burdened both the developers, the users and the gnu/linux distros - with constant problems that they're just getting fed up with.
contrast this with the fact - the FACT - that if you grabbed a random 20-year-old Microsoft OLE (COM) / Active-X (COM) DLL from anywhere off the internet (assuming you can find it), and you tried dropping that Active-X component into I.E. 10 or into the absolute latest-and-greatest version of microsoft office, guess what will happen? IT WILL FUCKING WELL WORK. ... does that drive the point home? do you understand now that saying "you don't know how x11 messaging or d-bus work" is a) failing to appreciate that i know a fuck of a lot about inter-process communication b) entirely missing the point.
x11 messaging only works because it hasn't really changed significantly. even if you use x11 messaging for general-purpose communications, you *still* have to create backwards-compatible APIs, and i don't imagine that x11 messaging offers any significant assistance in doing that (otherwise i would have heard about it, a looong time ago).
backwards-compatibl
Nope. This is just more of the same nonsense where Apple fanboys try to pretend they and their platform are more significant than they really are. They are the same underappreciated road kill that we are. No amount of kidding themselves will change that.
Their platform lost and is now pretty much abandoned even by Apple. Even Apple has moved on to the next thing where they have a prayer of being successful.
A Pirate and a Puritan look the same on a balance sheet.
For the average user, not the technical wizz-kid: the average user, Linux was never an option. Id didn't come on their store-bought PC.
So far so good.
If didn't "just work" (ever!) and it didn't support most of the peripherals or USB devices that they had or wanted.
Fail. Linux does "just work" and it supports every perepheral and USB device I've plugged into it. Take my Bluetooth USB dongle: drivers and install program for Windows and Mac, but nothing for Linux. Surprise, plug it in and it works. No programs to install, no drivers to install, no reboots, just plug it in and shoot pics to it from your camera or phone. Windows? Install program, reboot, install drivers, reboot, fiddle with it... and it sorta kinda works.
Blaming Linux's failure to penetrate the average household on anything but it's own lack of marketing
Indeed, that's the kicker. Most non-nerds haven't ever even heard of it.
polish
If you mean "pretty" you have a point. If you mean "well written and well behaved" you're wrong. For example, hardware fault-tolerance. Linux will work on flaky hardware when Windows won't even boot. And it seems that there are bug fix notifications almost every day on my W7 box, seldom on my Linux box.
self-discipline
I have no idea what you're discussing here. Whose self-discipline?
ease of use
Wrong again. Linux is far easier to use (unless you're using the wrong distro for the job, don't expect to play MP3s from a server distro). In Windows, almost every update, bug fix, driver fix, and every single software install requires at least one reboot and often more. Linux? No boots needed unless you're replacing the kernel or hardware. Shut your two computers down for the night, the next morning your turn them both on. In the Windows box, you have to log on (unless you stupidly left it without a password), then open each and every program and document you had open when you shut it down. Meanwhile, all you had to do with the Linux box is press the on button, it's sitting there like it was when you shut it off.
Installing a new program? In Linux, open package manager, enter sudo password, find app, click, done. Windows? Search for it on the web, download, double click the install exe, click "yes" to half a dozen UACs, then reboot... and probably reboot again, which of course means opening all your apps and documents all over again. How in the hell is that more user-friendly?
How is Windows more useable in any way whatever? Remember, I've been using Windows for over fifteen years and Linux for ten; I know the strengths and weaknesses of both. No way is Windows even close to Linux in useability. What Windows takes ten clicks for, Linux usually takes two.
support
True, the Geek Squad doesn't work on Linux computers. But a Linux computer, not having much of a malware threat, and lacking that god damned registry, seldom needs any support at all. It just works.
brand (i.e. not having a million different distros: all the same, but different)
That's only detrimental to someone too stupid to eat at any reataraunt but fast food, because OMFG THAEAR IS TOO MANY CHOICES!!!! You would rather Ford only carried Fusions, because having to choose between an F110 or an F150 or any one of the many sedans, or any of the many SUVs is just too much for your tiny little mind? This is the stupidest argument you Windows apologists use, and it's embarrasing on a supposed nerd site.
or integration
I prefer interoperability and industry standards to vendor lock-in. Again, that's a stupid argument.
If your comment teaches us anything, it's that Wndows is only for the learning impaired.
Now go tell Steve to throw another chair, I'm sure his office is only a few floors from yours.
Sheesh.
Free Martian Whores!