|
|
|
|
|
by gamble
5481 days ago
|
|
Desktop Linux doesn't have a learning curve; it has a learning cliff. Linux cribs so much from other operating systems that it's reasonably familiar and easy to use when you first sit down, but the problems start when you need to go beyond using it as a dumb terminal: perhaps you need to set up a printer, or there's an issue with networking or power management. Now you're over the cliff. It can be a nightmare for a engineer like myself to fix problems, even though I've been using Linux since the mid-90s. An unsophisticated user would be finished. An anecdote: I'm mainly an OSX user now, but I bought an eeePC netbook a couple of years ago for travel and tried to install the then-current version of Ubuntu. This was literally one of the most popular laptops on the market, and Ubuntu installed without a functional network device. Getting it working was not easy, involving a couple of reinstallations. Even then, power management was nonfunctional and the netbook got half the battery life as it did under Windows. The real problem with desktop Linux isn't that it's hard to use or different; it's that the average user can expect to struggle with crippling bugs and hardware incompatibilities that are a nightmare to fix. |
|
I hear this a lot, but nobody ever actually describes the problem they have. You mentioned priting. On my minimal Debian box, you point your web browser at http://localhost:631 and click shit and then the printer works. (If you want to improve print quality / feature support, then you probably need to google to decide which driver is best.)
On my Ubuntu 11.04 box, you type "printing" into the thing at the top left, click "add printer", click "network printer", click "find", and click "ok". That's it. Then you have that printer in every application, and from the command line via lpr.
It can't get any easier.
The only way you can run into problems is if you buy a printer that's not supported by Linux. And I think that's where most people run into trouble -- they buy something unsupported, and then spend three months googling in the hopes that maybe it's not really unsupported. One time in ten, it turns out that it is. The other nine times lead to stories like "Linux never works".
Nope, shitty hardware never works. Linux just hides that from you less than Windows.