Slashdot Mirror
Asa Dotzler on Why Linux Isn't Ready for the Desktop
An anonymous reader writes "Asa Dotzler of The Mozilla Foundation compares the explosive growth of Firefox to the anything but explosive growth of Linux and what it needs to do to get there for the "regular user" AKA mom, dad and grandma Bootsie."
All presupposing (as is so often done) that the ultimate "goal of Linux" (thereby attributing to "Linux" intentionality that it no doubt does not possess) is to woo Windows users away from their desktops, rather than to provide a superior computing and data processing platform.
I am very happy with the latter, which Linux has provided me with for some years now, and if Linux ceases to do so in favor of attempting the former, I'll happily switch to some other platform (until "I hate elitsts" n00bs who want to be elite but don't want to work for it invade and begin to transform-to-inefficiency that one as well, at which point I'll move on yet again).
Give me efficient computing or give me death. I want to manage my reams of data and my network tasks. I don't care if it jives with the [utterly inefficient] way of doing things in Windows, or if the Windows users care to adopt my methods.
I just want the powerful tools, unpolluted, task-oriented, intelligently designed, that let me talk to my computer using the language through which it can most quickly and subtly be isntructed.
It's not an elitist view, it's the view of a data processing pragmatist with a lot of tasks to juggle and a lot of work to get done.
STOP . AMERICA . NOW
First of all migration is raised as an issue: "When Regular People fire up the Linux desktop for the first time, the browser, office suite, email client, IM client, file manager, etc, each need to carry over as much as possible of the Windows application settings and all or very nearly all of the user data."
First of all that's a steep ask, but secondly I just don't think it's necessary. If that was required for people to switch no one would ever move to Apple. It's definitely a nice idea, and in the "nice to have" category, but I don't see that it's a deal-breaker.
The second point is API stability: "A user should be able to install Fedora Core 4 and go grab the latest Firefox release from Download.com and have it work without the need for finding and installing compat-libstdc++ or whatever."
This one is fixed - if developers would actually pay attention. Autopackage allows developers to package up their application into a self installing executable that can do dependency resolution. At that point not having compat-libstdc++ is the developer/packager's fault: they ought to have included an Autopackage for it in their repository so the installer can fetch it if it finds the right version of compat-libstdc++ isn't already installed. Better still, the people at Autopackage provide relaytool which allows developers to smoothly fallback to other library versions: for example, you can have your binary use the new GTK+ file chooser if it is available, but fallback to using the old one if it isn't. Which is really saying that the problem has been solved, it's up to the developers and people releasing the software to make use of the tools available.
The third point is preferences: "Gedit has about 30 user preferences spread across 5 tabs in a preferences window -- Notepad has about three."
Now that's not a great example becaue Gedit does a hell of a lot more than notepad, but I think the point is still very valid. To be fair I think GNOME has been putting in a lot of work on this front, and trying to clean a lot of these things up. That work is ongoing, and we can expect to see continuing improvment. That is, the way forward has been laid out, it's just a matter of continuing down the path.
The final point is "comfort":"The final major issue is comfort. Linux must feel comfortable to Windows users. Most people using computers today have been at it for a while now and they've been at it on Windows. Don't mess with their basic understanding of how things work."
I have to say, I think this one is a little dubious. If there is a better way of doing things why not do it? I think constraining yourself to the way Windows does things is a little pointless. There are plenty of things Windows does well, and it's fine to follow those examples, but there are plenty of things Windows does badly, and slavishly copying broken behaviour really doesn't make much sense.
I think the real point here is: be patient. I think the points are valid, but they are also largely well known, and being dealt with. Linux on the desktop is not going to "take off" anytime soon, but the rate of improvment in desktop Linux is tremendous, and it is making slow but steady inraods. Software installation (which has been the recent bugbear that people complain about) is looking quite good with Autopackage and Smart, but both of those are very new and it's going to take some time before a lot of stuff shifts over - that's life. GNOME is working hard on the preferences trim down and clean up, and, I think, is workign towards a fairly clean easy to use Desktop. KDE is headed in a different, but equally valid and interesting direction - I think the divergence is going to end up providing some real significant choice. Finally I think once all these bits properly fall into place and desktop Linux manages to make a dent in the enterprise (which seems to be where the major distros
Craft Beer Programming T-shirts
Which will, finally, result in power users and gamers having Linux as an option. That means that the latest hardware will be released with good Linux drivers and the games will be available on Linux. The biggest problem here is the Microsoft desktop monopoly.
Uh, no. I'm one such power user, and the problem with Linux is that moderate customization requires intimate knowledge of the command line and Linux's quirks.
I'm an XP man, but when I used a PowerBook for two weeks, I could easily install and remove programs, connect my external hard drive, and had some interface customizations up and running in a matter of minutes.
Compare that with my Linux experience: Two months ago, I installed Kubuntu onto my laptop. It's very likely that all of the issues that I ran into are easily fixable, but the solutions were simply not apparent or mentioned on all the help sites I went to. Let me tell you one thing: Most people don't like recompiling the kernel, compiling programs, or compiling drivers. It's probably a simple process (I've never had success with it myself), but it simply should not be required for usability purposes.
First issue: Installing software. This blew ass. First, I had to find out the name of the package, and tried to use apt-get. This didn't pan out. Then I found out that the servers that apt-get was trying to use were disabled, or something to that effect, so I had to go and edit a text file to allow for this. This pissed me off quite a bit, because had I not been dual-booting Windows at the time, I would have had no way of knowing how to fix it.
Second Issue: Getting my wifi card to work. This was fairly important, as my connection utilized my campus's wireless. So whenever I had an issue, I had to reboot into Windows and search for it. I never managed to get it to work, even though I have one that's fairly ubiquitous (Intel 2100). After futzing around with the command line for a couple of hours and browsing some sites, I tried to figure out how to install the drivers derived from the intel open-source release. Then I foudn I'd have to compile the drivers or whatnot, and I gave up there until I could find someone experienced in the matter.
Third Issue: I couldn't get it to sleep. I spent a good 40 or 50 minutes to find out that I needed to recompile the kernel to include support for sleep.
Fourth Issue: Realizing that I had just wasted my time installing Linux. I could do everything I could do in Windows, except it took me twice as long. Screen space was a serious issue. Using OpenOffice at 1024x768 felt like using MS Word at 640x480. My screen always felt cramped. Image editing in GIMP just sucked. Even when using Photoshop, I felt that 1024x768 wasn't sufficient for some of the stuff I was working on, and using GIMP made me feel like I was working at 800x600.
Obviously, I'm back to XP. I'm willing to spend the extra $300 to save the time and frustration that I've had using Linux. I realize that pretty much all of these issues are 'trivial', but the fact that I ran into all of these problems in the span of two days seems unacceptable. When I used OSX for the very first time, it took me less than two hours to become proficient. XP took me 4. Linux needs to get to the point where a power user like myself can be quite proficient over the span of a day.
You claim to be a power user, but you had problems with your wireless card and power management.
I said that power users would be the last segment (#4) to move to Linux because they wouldn't be happy until their hardware was supported.
I run Ubuntu and it runs great on fully supported hardware. But then, I also run my LCD screen as 1280x1024 so I don't have the space problems you do.
I might as well comment on this since health care came into it.
Most hospitals use Windows exclusively for user interface boxes. Their backend systems use things like AIX, Linux, or some other flavor of UNIX to run the databases and such. The catch is that universally these user (Windows) systems are overloaded, cumbersome, full of security holes, and a total mess.
Take a real life example of a hospital system that has one major inpatient facility, and a bunch of outlying clinics. Their backend uses some UNIX variant, and they use some Windows program to interface with it. So far not bad. Enter the problems.
First off, there is no unified user home directory system. (Yes, Windows can do this.) Under UNIX, the simplest way to handle it is do a networked stock setup of all the user machines, mount home directories under NFS (or preferably something better), and avoid a lot of problem. This helps with data security, because patient information (e.g., the progress note I just typed in Word) is saved under my user account with default permissions of -rw-------. Second, this means that if I go to one of the outlying clinics, I can still access my files.
I've actually thought really hard for a few years now about why these hospitals blow literally hundreds of thousands of dollars on Windows machines, when they could set up Linux machines that are better administatable for much less. After they set this up, they have to deal with all the random crap of people violating the security protocol by installing God only knows what (Gator, anyone?) which, even if it affects only their account, is still a problem.
But perhaps the biggest problem with Windows in these environments is this: The things take so god awful long to log a user in (two minutes at least at my last place of work on a 2GHz box) for whatever reason that much of the time people don't even bother to log in and out. That leaves a terminal sitting there, and makes the password protection at the OS level worthless. (Yes, obviously something is wrong with all these installations -- probably Novell -- but it's universal. I've never seen a Linux installation that bad, EVER, in ten years.)
One machine I have has a DLink wireless card in it. I installed the acx_100 driver, which seems to be the driver for it. Unfortunately, the manufacturer has some bogus "feature" in the hardware that causes the network card to reset itself every so often. When that happens, the network card drops off the net, and doesn't come back up until a reboot.
The proper thing for the manufacturer to do is either release a Linux driver for their card, or document the incompatability so that I can hack support for it into the driver and release it. In this case, I've done the work for them, for crying out loud.
By the way, I did call the DLink cretins and ask about this. They knew nothing. Their answer was that they don't support Linux. When you release hardware, either release drivers for the predominant operating systems (which is now Linux and Windows), or at least have the decency to release the specs so someone can cover your lazy ass. They don't do this.
I think they honestly think that someone isn't eventually going to get pissed off enough to reverse engineer the damned card, which if I can ever isolate the problem I'm going to do and blow all over the Internet, along with a message proclaiming how much their company sucks.
BroadCom is another one. They release no information about their cards, and lock users into them by building them into the laptop. So you buy a new HP laptop, and its wireless card is a BroadCom. Oops. Sorry.
So I suppose when XP doesn't come by default with drivers for hardware released two months ago that it too has serious support issues?
XP won't come with drivers for hardware that has come out after its release. The manufacturer provides the drivers. So if hardware manufacturers can provide drivers for XP is it unreasonable for them to produce Linux drivers on that same CD? On top of that they go to great effort to provide it in the format requested by MS themselves to be compatible with their OS.
Is it unreasonable for them to provide a linux driver in the format requested by Linux developers?
Is it reasonable to blame the Linux distro and not MS even though both haven't included the driver in the default install?
I don't see how these two situations are really different? XP needs third party driver for your card to work. Linux needs third party driver for your card to work. If anything, it's up to the hardware manufacturer to make sure the user experience is the best it can be. At the moment, they don't seem to be trying all that hard...