Slashdot Mirror
Linus Torvalds: 'I Still Want the Desktop'
darthcamaro writes: Linux has clawed its way into lots of places these days. But at the LinuxCon conference in Chicago today Linus Torvalds was asked where Linux should go next. Torvalds didn't hesitate with his reply. "I still want the desktop," Torvalds said, as the audience erupted into boisterous applause. Torvalds doesn't see the desktop as being a kernel problem at this point, either, but rather one about infrastructure. While not ready to declare a "Year of the Linux Desktop" he still expects that to happen — one day.
All Google has to do is dump that stupid steaming pile called ChromeOS, and admit that Android wins. A desktop customized version of Android (complete with a real desktop) is still based on Linux (at least Google's fork of it), already has hundreds of thousands of apps, and could be better in nearly every way than Windows or Mac OS-X in 2 years, IMO.
The other broken OS, GNU/Linux, needs a major overhaul before it will ever be popular among anyone but geeks who are willing to accept that their OS is hostile to sharing new apps, or too blinded by fan-boy-ism to notice. I write this from my Ubuntu laptop, where my code contributions are far lower than Android or even Windows, even though I put in most of my effort here. It's just easier to publish an Android app. It's even easier to publish software for Windows. If Mark Shuttleworth were just a bit smarter, I think he'd realize he needs to abandon managing .deb packages and start this whole mess over based on a more git-like aproach. He's done a lot in that direction - user PPAs for example, but it's still not there. No RPM or .deb based Linux OS will ever become the basis for the Year of the Linux Desktop.
Celebrate failure, and then learn from it - Nolan Bushnell
Well, to an extent he's right; the kernel does what kernels do, and that is, talk to the hardware at the lowest level. It does that just fine.
Unfortunately the stuff piled on top of it is either not keeping up with trends (X and the way modern video changes on the fly), or not really good at handling what a user would want automagically.
I attempted to use the most integrated desktop with vanilla Ubuntu 14.04, but I found its window manager to be so restrictive as to be useless to me. It handled a lot automagically, but not what I wanted, and it was also very unclear how to go about getting to what I needed to change. It wasn't even intuitive on how to bring up a terminal window, for example, which is basically the bulk of what I use Linux for.
The lack of documentation is also hurting, badly. I'm working on building a multiseat box at home and LightDM was redone sometime between Ubuntu 12.04 and 14.04, and there wasn't any good support documentation explaining how the configuration files now work. I ended up switching to kdm even though I'm not using KDE, just so that I could configure a display manager that would actually work right.
I think that the golden age of FOSS documentation is over. For a long time Linux and other FOSS docs were based on how commercial UNIX documentation was written, but slowly more and more developers aren't creating volumes of use or configuration docs in the UNIX model anymore, and as few UNIX-era developers work on Linux and other FOSS, there are less people who remember how those documents were made and why. I think that is what will hurt FOSS the most, simply being unable to figure out how to do the things that one wants to do because the docs don't exist.
Do not look into laser with remaining eye.
Successful desktop operating systems have been based on various kernels. Apple used a pretty crummy one before switching to a BSD derived one. The Atari ST and Commodore Amiga each used their own, and they had certain success in their niches.
The problem is the GUI. People don't like X, and Linux people have no desire to give us anything else. Engineers and enthusiasts may well argue that it's better from various objective reasons but the end user doesn't care. They use it and they think it sucks. Perhaps the problem is that it still pretty much needs the shell. Perhaps it's large, slow and clunky. Perhaps it's the poor support for games.
Android doesn't have these problems because the developers didn't cripple themselves with X. TiVos and Tomtoms (before switching to Android) used Linux without X and people were quite happy with them.
Give us a nice, simple, standard GUI without a bazillion customisations, and with the ability to to just install an app from the GUI and run it from the GUI, and Linux might actually work on the desktop.
They used to have a link to an OpenSuSE live CD to do just that (well, with XFree86/X.Org. Wayland isn't a priority for KDE). It would appear that is no longer present on the site. Also, KDE doesn't really care to be Linux - they target UNIX compatible systems (AIX, FreeBSD). GNOME, on the other hand, wants to be just Linux, and is largely in bed with the Fedora Project.
I'm starting to think GNU is the problem with "GNU/Linux" these days.
I think the main problem is that Linux is *TOO* configurable. "Normals" don't want hundreds of options. They want people to tell them which of a limited number of options will work for them.
Which distro should I pick? Which window manager should I pick? How do I configure my computer to be optimal for *ME*? I'm a techie and I can't tell you which distro is really the best for most people. I can tell you which ones are more stable.....but it isn't just ONE.
With Windows....and even Apple.....those choices are more or less made for you. All a "normal" needs to do is decide which apps they need to run and whether their OS supports those apps.
As a monopoly, Microsoft gets to hold the proverbial "gun" to device vendors heads and say, "support our OS on our schedule exactly how we say we'll fucking destroy your market and feed you to your competitors". Thus, Windows drivers get support from device manufacturers. Linux device drivers come from begging, pleading, and sometimes reverse engineering and all volunteer efforts of the open source community. Sometimes this happens despite hostile responses and legal threats from device vendors. My hope is that some day Linux will get to wield that gun...
*** Sigs are a stupid waste of bandwidth.
Superior by what definition? Stability? sure, I'll give you that. ease of use?
1. Take a random Windows XP user.
2. Sit them in front of two machines, one running Window 8, one running Linux MATE.
3. Ask them to start a text editor on both machines.
4. See which one takes longer, and results in more bitching and swearing.
I mean, seriously, if I didn't know about Windows+R, I wouldn't have been able to start freaking Notepad on the Window 8 machine I played with in a local computer store.
This means that you have to have code review from the Linux kernel team. And you have to divulge any amateur or buggy code embodied in the source. Which may compromise the imaginary advantage your marketdroids think they have on other platforms.
God yes this. 1000 times this.
One particular example I remember well was TV capture cards in the early/mid 2000s.
Basically the chipset was the Brooktree BT878, which was actually pretty good though remarably cheap. I ended up with a few capture cards what people gave to me because "they didn't work".
That meant they didn't work on Windows. Every manufacturer wrote their own buggy, unstable, system crashy drivers and put effort into some god-awful shiny TV program which made heavy use of gradients and nonstandard TV controls.
On Linux, they all. just. worked. There was one BT878 driver that was well written and well debugged and "shitty" capture cards that "didn't work" gave years of stable, flawless performance.
The same thing cycled around with webcams. It was a wild-west of chipsets. They'd all work after a fashion on Windows. On Linux, they either worked perfectly or not at all due to lack of drivers. The ones that did work were invariable more stable and more featureful because the driver would be written to expose the full functionality of the chipset.
These days the situation is better on all platforms since the standards people have realised that having standard driver interface makes for a much better experience. xHCI means that any random USB chipset works. Same for bluetooth now too. UVC means any camer works and so on and so forth. It's like magic. You can buy a cheap-ass piece of crap from any random vendor and it will just work, no drivers, no hassle on Windows, Linux and OSX.
The thing is vendors are almost uniformly bad at writing drivers. On Linux this means they don't bother. On Windows the drivers are a pile of crap. Having centrally maintained drivers is in fact a large improvement on BOTH operating systems.
SJW n. One who posts facts.