Slashdot Mirror
Top 10 Things Wrong With Linux, Today
An anonymous coward sends in this link to a list of the top ten things wrong with Linux today. He's noting things that are "wrong" not with Linux per se, but with a user's experience with Linux; most of his points actually have to do with KDE/X. The KDE 3 bug he's talking about is a user-interface change in konqueror: form elements can be changed by mousing-over them and turning the scroll wheel, which is very bad. Hopefully the KDE guys will roll this change back to the previous behavior.
1. No 'best' browser.
Gosh, how about the nice thing we call choice?
If they were all very good at doing what they do - that's fine. Sadly, they're not. Whenever I'm in Linux I *always* yearn for IE when I'm browsing, no matter what browser I use. The author's point is that all the current options aren't that amazing, and all have pretty big faults.
2. Prompting for a filesystem scan.
Damn, if only this was adjustable, oh yeah...
Not the most obvious thing in the world to change though - and something IMO the default should be automatically done in the background.
3. Printing needs to be easier to configure.
It can't get much easier that printconf (for Red Hat users).
Ok, in Mandrake it was pretty easy to get my printer working, granted.
4. Make it easy for the user to find out how to do things.
Yeah, reading a book or taking a class (or searching online) is so hard. When will people realize that a computer it a techinical thing? You have to be willing to do a little homework, even with a mac (if you've never used one).
Yeah, good viewpoint. Why make things easier and more intuitive when the users could just get off their lazy asses and go study to use the machine!
Please. Most people will pretty quickly pick up Windows, and most things are pretty easy to work out how to do. There are stable, easy to use, tried and tested configuration screens that work. Complexity and a steep learning curve does not bring superiority.
You don't have to lose power and control by making things easier to use.
5. Cleaner redraws.
Ok, sure.
6. Die stray processes, die!
Ever tried ctrl-alt-escape in KDE?
Obvious and transparent, no?
7. Easy way of sharing files.
You like in windows, where I find places like Doctors offices "sharing" all their patient records on the internet? Check out programs like share sniffer if you want to find them too.
So, because some people stupid, things should be made much more complicated than they need to be for everyone else? Cars should be made harder to drive - keep all those damn idiots off the roads.
Yeah, right.
8. Sound support.
Ok, if you want professional audio production cards, you got me, but for most other sound cards there just isn't a problem.
I can't say I've had much of a problem with my cards, but they've been pretty standard items.
9. No common editor which supports "soft wrapping."
Well... pico does this (ctrl-j)
You'd have thought more of the more popular editors would have it (at least as an option). It's a pretty basic thing to have.
10. No easy way to configure X - especially change resolution on the fly.
Actually, it couldn't be easier to change resolutions on the fly. Hold ctrl and alt, then hit - or + on the numberic key pad. This cycles you through all your selected resolutions, on the fly. Just make sure you selected all the ones you want when you setup x (Red Hat users use Xconfigurator to select resolutions).
Couldn't be easier? I beg to differ. Once you *know* that you press that combination, and you've already gone through the process of having all your resolutions and refresh rates configured, yeah, it's easy. What really *is* easy is this:
Right click on desktop -> properties -> settings
[or Start -> Control Panel -> Display settings]
Drag the slider to the resolution you want. Select colour depth. Press OK.
No text config file that you need to setup with all the options your system can support.
Yes, Linux should be more powerful and dynamic than Windows - that's part of the whole point of it. However, things can be easier without the expense of control.
As you are probably aware, cut-and-paste in Unix/Linux desktop environments have traditionally relied on X to do the dirty work.
The problem with this approach (which Microsoft, Apple, etc. recognized back in the '80s but we still haven't caught up with) is the notion that text is not the only thing that needs to be cut, copied and pasted among and across applications.
Thus, there is inherently a different semantic involved when transferring objects other than text, because X doesn't know how to handle those.
X knows nothing of moving a picture between a charting application and a word processor, for instance. Nor should it.
In order to make up for that deficiency, we're faced with a conundrum: do we take the functionality away from X and hand it to the higher-level desktop environment, or do we go with a hybrid approach, letting X still handle the "plain-text" cut-and-paste functionality and letting the desktop environment handle the rest?
I argue that the hybrid approach is terrible for users, as it adds yet another conditional rule users have to follow when trying to complete a task. This, I believe, was what the author was trying to communicate.