Slashdot is powered by your submissions, so send in your scoop

 



Forgot your password?
typodupeerror
×

Why the World Is Not Ready For Linux 861

eldavojohn writes "While many users reading Slashdot embrace Linux, ZDNet is running an article on why the rest of the world isn't ready. One note for Linux developers: 'Stop assuming that everyone using Linux (or who wants to use Linux) is a Linux expert.' While a lot of these topics have been brought up as both stories and comments on Slashdot, this article pretty much sums up why Vista could be absolutely terrible, and people would still believe there is no other option." From the article: "The one area of Linux ownership and use where it becomes apparent that there's an assumption that everyone who uses Linux is an expert is hardware support. Your average user doesn't have the time, the energy or the inclination to deal with uncertainty. Also, they usually only have the one PC to play with. Hardware just has to work. There's a very good reason why Microsoft spends a lot of time on hardware compatibility — it's what people want."
This discussion has been archived. No new comments can be posted.

Why the World Is Not Ready For Linux

Comments Filter:
  • by Asmor ( 775910 ) on Friday November 03, 2006 @12:46PM (#16704245) Homepage
    I've just recently installed Linux on my home system and really tried to figure out. And I've gotta say, the whole thing sucks. I've tried Fedora and Ubuntu. Fedora installed much easier than Ubuntu, although that's partially because Ubuntu was installed to replace Fedora. Fedora, however, had an option to automatically remove all Linux partitions and install there, while Ubuntu's only analog (and default even if there's plenty of unpartitioned space) is to delete the entire drive! Not something I'd want to do when I'm dual booting.

    From there, things just got worse. I spent a long time researching how to mount an NTFS partition in Fedora, finally found some good links for Ubuntu (hence the change). I managed to mount the NTFS partition and listen to the music stored thereon, but I really only had a vague idea of what I was doing. Some of the stuff was reasonably obvious. For example, the fstab file is obviously supposed to be default mountings when you boot up. However, the syntax used inside of it is all gibberish to me, as was most of the commands I used during the process of installing everything I needed for this project. I basically just copy-pasted everything, filling in specific information like /dev/hdb1 when neccessary. I don't know what the -l in fdisk -l means. Hell, if it weren't for using it in DOS I wouldn't even know what fdisk was. I don't understand the commands that I used to grab the software from the internet.

    And every single tutorial is exactly the same. They either assume you know something, or they tell you what to do without explaining why you're doing it. It'd be nice if there were some tutorials that actually took the time to tell you, for example, "fdisk -l" invokes the fdisk program with the -l switch. Fdisk is used for viewing and editing partitions and the -l switch makes it (I assume) list the current partitions.

    I installed Linux so that I could learn how to use it, but all I've learned is how many arcane commands with even more arcane syntaxes (syntaces) it has.

    Keep in mind, also, that I'm the exception. I'm a Windows user with no practical interest in Linux, who's only doing it for the learning experience. I'm actually willing to go out and look stuff up, to some extent. As I said, though, Linux is just a curiosity to me. I'm not going to spend all day figuring out how to exit the "help" given by the man command (seriously, how do you exit it? Aside from closing the terminal, I mean? I know I can prest shift+zz because someone told me that, but how the hell would anyone ever guess that?).

    Linux, even the best distributions, have a long, long, long way to go before they're anywhere near as usable as Windows.
  • by CheeseburgerBrown ( 553703 ) on Friday November 03, 2006 @01:40PM (#16705403) Homepage Journal
    The best thing about my new car is that it's free, which really jibed well with my bank account status.

    The first bad news came when I tried to actually get in the car and drive; I received an error message on the dashboard that said, "No tires detected."

    I got out and checked, and there were tires on the car, so I got back in and punched the steering wheel a few times. After a few hours of poring over the manual I discovered that I had to tell the car about what kind of tires I had, so, after some digging, I found the button to initiate tire declarations (for some reason it was called INI RUBBER-BASED ROAD INTERFACE LIB EZ). I pushed it and a little sign lit up saying, "If your Linux car is a 2006 model or better you may need to install a rubber-based road interface synchronizer before attempting to declare tire status to the vehicle."

    I went to the hardware store and bought one, but it was the wrong size so I had to go back again. The instructions were in German but I still managed to wedge it in there. I pushed the button and went on with my tire type declarations, after which the car decided to recognize my tires.

    Great, I thought -- now where's the gear-shift?

    After hours of searching I gave up and called up a friend who's a real car expert. He chuckled. "Dude, only idiots use gear-shifts. Linux drivers use gear modulating paddles located on the sides of the driverseat. Don't you know anything about cars? Jeez."

    I made fun of him for being a virgin and then returned to my car. Indeed, the gear modulation paddles were conveniently hidden under the edges of my seat.

    I decided to take the car for a spin, so I pulled out of my driveway and the car stalled. A message on the dashboard said, "Before initializing for road driving, please specify your exact model of Linux car."

    It then gave me a list of four hundred vehicle types, each with just a slight difference in model number. I was eventually obliged to take apart a substantial part of the engine in order to see the little model number on the side of the block. Satisfied, I inputted this number into the dashboard once I'd put the engine back together and started off on my first Sunday drive with my brand new Linux car.

    Then I found out my car wasn't compatible with my iPod so I put the fucking thing up on cinderblocks in my front yard and took the bus.

    The bus sucks, true, but you know what? It's a no-brainer.

Intel CPUs are not defective, they just act that way. -- Henry Spencer

Working...