|
What sets companies aside from the Linux "community" is support.
While there ARE good Linux users, many of the hardcore ones have only utter and complete contempt for those who are less proficient than they themselves.
I believe it's called a god-complex?
When asking for advice on getting something to work at all (let alone properly), the typical answer will be something along the lines of "RTFM, noob", in other words "don't waste our time and go play elsewhere".
Of course the manual referred to is the manpage of the program in question, which is all the documentation the gurus claim is needed for a perfect understanding of the operating system and its concepts.
Now, if the system were as userfriendly in its installation and use as is Windows or MacOS (for the average user) there would be little problem with such an attitude (how many people call Microsoft tech support asking how to get their printer to work?) but Linux is anything BUT that simple.
I spent 5 months (from september last year to january this year inclusive) attempting to get my laptop set up with Linux.
After about 3 weeks I stumbled upon a website that gave me some crucial hints which got it working, sorta.
I still had no network and the video was unstable, but at least I got a prompt where I could type the reboot commands when things went bad again.
Then I found out that the source for my troubles: the network, USB and video modules I needed depended on incompatible versions of core libraries AND were broken in different versions of the kernel.
In other words, there would be no way whatsoever to get the machine working at any time.
I decided to pull the plug at that moment and reinstall Windows 2000.
Not needing any support from anyone I had the machine installed, running, and fully updated with all needed servicepacks in under 2 hours (most of which was spent waiting while it copied data from the installation CD or the internet).
I've been working professionally in IT since 1997 (and as a hobbyist and student since the late 1980s), and I can't get a simple machine (no ultramodern hardware, it's 4-5 years old) working despite knowing my way around the only source of information available: the internet (and that with a second machine running Windows to access that information, remember one of the problems I had was with networking...).
How is someone who has no other computer connected to the net, no experience with arcane command prompts (mind, I like command prompts but many people have never seen them and don't want to), and not versed in the spitting inside sourcecode and logfiles going to get even as far as I did?
If they give up in frustration after a day or two I can perfectly understand that.
|
What sets companies aside from the Linux "community" is support.
I have an open source project (Quanta Plus) with a mailing list. On it are developers and over 200 users who typically respond to user questions in a matter of minutes. Developer answers are rarely more than a few hours away and if a problem is not readily resolved it becomes a priority to fix. Please tell me a commercially supported project with an average of 10 bugs or less open at any given time where you can talk directly with the developer and get a response besides "reboot and reinstall" from a telephone in less than 10 minutes. What are you smoking?
I've been working on computers since before the microprocessor and I watched the rise of MS. They reject the "goto" statement in code but that is all their manuals are. This is to get you to buy books from MS Press. But when you call them what do you get? Wait, run around, condescending treatment. Everything from the little nagging wizards to the obfuscated install procedures is all designed to insult your intelligence and make you feel stupid.
When asking for advice on getting something to work at all (let alone properly), the typical answer will be something along the lines of "RTFM, noob", in other words "don't waste our time and go play elsewhere".
We have probably well over a million users of our software. We also have a very good and through manual for our program which answers most questions. Since you didn't pay me for it can you explain to me how I can answer questions for several thousand new users this week who are too lazy to take step one and read the docs? Kiss the project goodbye, as well as my having time to put a roof over my head. Some developers may lack a little tact but I should point out that there is nothing wrong with being a n00b. Only someone with ego problems intent on leading a boring life considers ever being noticed as a neophyte at something again to be an insult. I'd rather be a green growing new sprout than a petrified stuffed shirt.
I spent 5 months (from september last year to january this year inclusive) attempting to get my laptop set up with Linux.
I'm guessing you didn't do much reading before either. I've installed Linux on dozens of PCs from 1999 on and had very few problems. Nothing really out of the ordinary that wasn't resolved in a day or two. I know a lot of people who've put it on laptops too. However there are some very non standard systems out there. For some time newer ATI video boards just weren't supported and a friend of mine was unable to get it to run, but fortunately ATI has taken a turn for the more enlightened and now they are much better supported. This is pretty standard, though some companies insist on using one off weird hardware that is not supported they are fewer and fewer.
You can't blame an operating system kernel (which is what Linux is) or volunteer developers for not supporting what companies refuse to make available to them.
I've been working professionally in IT since 1997 (and as a hobbyist and student since the late 1980s), and I can't get a simple machine (no ultramodern hardware, it's 4-5 years old) working despite knowing my way around the only source of information available: the internet (and that with a second machine running Windows to access that information, remember one of the problems I had was with networking...).
I'm going to recommend that if you see any news items talking about the relative levels of software expertise between *nix and Windows admins that you just pass it by. Pay it no attention. It's got to be as difficult to believe as you and I talking about the same software. There is a reason that all those yellow "for dummies" books sold so well... Using MS software seems to somehow gum up your cognitive processes.
My guess is that your IT postion must be supporting people having problems with windows continuously breaking. My up times generally run between kernel upgrades and have exceeded a year. I don't get windows viruses. I only use the command line when I feel like it because I have KDE and webmin. I also don't make a point of saying bad things about others because I lacked the common sense to do a little bit of up from compatibility research. Something is supported or it isn't. Considering you can download and burn Knoppix on a CD, load it in your system and boot and see exactly where your support level is and try out Linux without touching your hard drive it's a real head scratcher how someone would torment themselves for five months without their notebook. At least it gives you something to rant about. Make sure not to rant to anyone with a cluestick handy though.