I am not a computer novice. I was programming in BASIC and PASCAL back in grade school. I remember accessing the "main frame" via a DECWriter. I was on the cutting edge of personal computing and had an IBM PCjr--with a color monitor. I did everything in DOS, and was a Mozilla user way back when it was still Mosaic, and IE wasn't even a wet spot on Bill Gates monitor. I've run Windows since 3.1, I remember when pine and gopher and archie. I remember having to actually hunt to find an ISP that had PPP. I write html and css by hand, and I'm president of a small web-hosting company.
This year, with the hubbaloo about Vista, I finally reached my breaking point and decided that I would not give Microsoft another penny for an OS that treats me as if I were both an idiot and a thief. So, I did my research regarding linux distributions, and I decided that Ubuntu would be a good place for me to start. It's supposed to be "linux for newbs". And, while I've been playing with computers for 25 years, when it comes to linux, I have to admit that I'm a newb.
I am, I'm sorry to say, less than impressed.
I used an old, mildly defective, laptop as my test box. I wiped the drive and (after some significant frustration finding an ap to burn an iso to CD) installed Ubuntu. The install was rather painless. I was off to a good start. The designer in me wasn't exactly ecstatic over the depressing brown desktop, but I figured I could get back to the "pretty" factor later.
Right about here is where things started to break down.
I had to have my sys-admin walk me through the process of getting the wireless up and running. Now, maybe I'm being a bit silly here, but I thought that 802.11 would be old hat to the linux community; a snap to get running. Yeah... not quite. Eventually, however, it was up and running. Great. Now I can sit down anywhere in the house and access my new and spanky-fresh linux box via VNC, just like I do for my antiquated (but continually useful) Windows desktop box.
Or not.
VNC works... when it manages to connect. I open the connect dialogue, select the right IP, click on "connect" and.... apparently I'm bouncing the signal off a relay satellite orbiting Tau Ceti. The connection just vanishes. When it does connect, it works great and holds the connection for days without a problem. Actually getting it to connect, however.....? It's an exercise in random probability.
Okay... my house is small and, for the most part, I'm only using the linux box as a juke (for now). So, I learn that USB audio is part of the kernel. Great. I plug in my USB speakers and get ready to listen to my music. And we hit snag number 2.
Yes, the speakers work. They work rather well...... on the rare occasion that the box actually manages to activate the USB audio component. {sigh}. I've taken to leaving the linux box running continually (which is a bit of a problem, since the box has a faulty power buss on the motherboard and, as a result, has no internal cooling; it's currently cooled by a USB-powered "chiller plate"), however, there are times when I need to reboot. It generally takes at least 5 reboots to get the USB audio to kick in. I'm not doing anything different each time, it's just a matter of random chance.
So... I have the box up and running, the USB audio active, the net connection connected, and--if I'm lucky--I'm able to control it all via VNC. So.... my mp3 library is on my NAS so that any computer on the network can access it and play the music. Any computer that is, except the linux box.
If I browse the network from the linux box, I can see my NAS. In fact, I can see all 3 partitions, which is more than I can do from the Win boxen. However.... my juke application doesn't see the NAS. Ah... I need to map the networked drive as a local drive. Right. So I head out to the net, do the Google magic, and..... come up with some unintelligible mumbo-jumbo that I'm supposed to type into the command line, and insert into some system file, and..... it still doesn't work.
Am I missing something here? In Windows, with the click of a couple buttons, I can map a network drive as a local drive. In linux I can't? The geek OS doesn't have a way for me to access networked drives? WTF??
And what's with all this command-line shit?
Let me get blunt here: You linux-geeks are always going on and on about how Windows is a tool of the Devil and linux is the Holy Grail, and how can people be so stupid as to stick with Windows when linux is obviously so superior?
The answer is simple: People want a product that works. A product that works the first time, without mucking about in the system files, and without having to learn a whole new language of commands. Not everyone is a computer geek. Not everyone is a sysadmin. Some people are doctors and lawyers and accountants and mechanics and bakers and parachuting instructors. They don't expect you to know how to do surgery or prosecute a tort case or adjust your fuel injection or decorate a wedding cake or pack a parachute... so you shouldn't expect them to know how to plug commands into the terminal window.
I want to switch to linux, I really do. But linux isn't making it very easy for me. I really don't think it's unreasonable of me to expect things to work correctly, consistently, and easily. At this point in my life, I have a spare computer and spare time and can afford to look at switching over to linux as "a long-term project". Most people don't have that.
If linux really wants to take market share away from Windows, you're going to have to get your act together, trash the geek-elitist attitude, and build an OS that works for everybody, not just geeks.
I'm going to continue to trudge through this--because I'm really obstinate--but I am not impressed, and until there are some significant improvements in the the "user-friendly" category, I will not recommend to anyone that they convert.
If you can't convert those who actively seek you out, how can you possibly hope to convert those who are happy where they are?