Slashdot Mirror
Perception of Linux Among IT Undergrads
iconian writes: "The Linux Journal has a story on IT students and their perception of Linux. One of the funnier myths perceived to be true is that 'Microsoft's technical support is the best in the industry and is superior to that offered by the Linux community.' It just goes to show how little real world experience students have. It's a bit disturbing considering they will be the next generation of technology workers."
One of my interns at work is a CS undergrad, and I think he's pretty typical of the breed. Talks about Linux all the time to be 'leet, but still gave me a resume done in Word on his pirated Win2K partition.
Schools are a tough nut to crack for OSS, because students have no moral qualms about piracy and a lot of professors demand closed file formats for assignments to be electronically filed.
--saint
>One of the funnier myths perceived to be true is that 'Microsoft's technical support is the best in the industry and is superior to that
>offered by the Linux community.'
While I can not speak to using the pay-per-use support of the Linux Vendors, if you use Microsoft's Incident based support system, It is really really damn good. I have not contacted any other Vendors where you can call w/ a technical support problem and speak to the developers of the application at 11:00 at night.
Please do not flame... I am not saying that the Linux community provides bad support. In terms of free support services, they kick M$ ass.... I am only speaking to my experience w/ Microsoft's Pay-per-incident support....
The students felt that "The KDE/GNOME choice confuses most newcomers to Linux."
This is listed by the author as a "clanger", or repeatedly offered mistruth. I wholehartedly agree with him. As an experienced Linux user, I feel that the KDE/GNOME choice does not confuse most newcomers to Linux, it confuses nearly all of them, as well as experienced users. What the students should have said was "the KDE/GNOME choice confuses everybody".
I'm so tired of having to decide which featureset I want to use today. For C++ development I use Kdevelop, because of the nice C++ features like picklists for virtual functions. However I can't stand KDE's tendency to map its' own colors onto my X applications, nor can I take it desktop switching mode, so for casual web browsing I restart in Gnome. This means that I've had to memorize two control panels, two ways of resizing Xterms (I hate both their Xterm replacements), two ways of virtual desktop switching, etc. If there's anything that's important about the desktop metaphor it is that the metaphor must be intuitive. The problem with choice is that it requires you to gain knowledge in order to make an informed decision. To gain knowledge you have to spend time learning. When I pick up a lab instrument I don't want to spend time learning how to use it's desktop; I don't freaking care how it works. I want to use the instrument.
The GNOME/KDE choice is annoying. Honestly I don't care which one goes away, I just wish one of them would.
If guns kill people, then CmdrTaco's keyboard misspells words.
This will probably get modded as flaimbait or something, but here goes...
From a corporate perspective, IRC is very, very far from legitimate or reliable tech support. Same goes for usenet. People want a phone number that they can call and get an answer RIGHT NOW. Or if they don't get one RIGHT NOW, they want to know that a technician is working on the problem until it's solved.
There's very little of such support available in the world of Linux right now. RedHat is getting there, and LinuxCare used to be on its way.(they're gone now, right?) So yeah, in the realm of Tech Support with capital letters, MS blows linux away.
But you're right. I get answers faster through IRC and/or USENET posts than though MS tech support almost every time.
-- Minds are like parachutes... they work best when open.
You're comparing Microsoft corporate support offerings to random hobbyist support offerings.
Wait, wait, for my next trick, I think I'll compare the support you can get from your 20-year-old son for Windows to a Red Hat corporate support plan.
It would be wiser to compare the support from an actual Linux company, such as Red Hat or IBM, to that of Microsoft.
What we call folk wisdom is often no more than a kind of expedient stupidity.-Edward Abbey
mysql trouble - $150-200 bucks and the trouble is worked out.
Redhat trouble - About the same.
Linux technical support is identical to Microsofts. you just have to ask the right people. asking in a IRC channel is NOT product support, you didint go to IRC asking about the MSSQL problems did you? why did you do the same for linux?
It's unfair comparasions like this that support the FUD out there.
Do not look at laser with remaining good eye.
My university (one of the top in the US, supposedly) just started teaching the intro CS class (for non-coders) using C#. Why? God only knows. They used to teach it in Java- they switched from Pascal very early on, which was probably a bad choice. But now Java is superbly well-documented, and becoming an industry standard. C# may become an industry standard, but only because MS is behind it. So now that course is essentially Windows-only. (The standard data structures and systems programming courses are, of course, still done on Unix- by now, of course, in the form of RedHat 7)
There are quite a few people who push Linux as the best and only solution. These people are dorks. However, most of us react more strongly to MS products being pushed as the best and only solutions because:
- MS software pricing is an obscenity.
- Linux companies haven't used illegal coercion to make their products the market leaders.
- Until recently, people did not choose Linux-based solutions simply because they had the word "Linux" in them.
- the possibility of single-vendor lock-in is virtually nonexistent for Linux.
I work part-time in tech support here, and I cannot tell you how annoying it is to have to deal with all the Microsoft fanboys who think Windows is the final point in computing evolution. These are techincally astute students, among the brightest in the world, and incapable of dealing with anything that doesn't have the Start menu and Explorer. For my part, I'm glad I'm studying computational biology, where MS products are by and large recognized as utter garbage. If Windows ever becomes the platform of choice for serious scientific computing, I'm going to law school instead.
I see a lot of posts here claiming new students only know about AOL, MSN, Office XP, etc. Can you blame them? When Mom and Dad by them their new Dell Optiplex GX150 with a TFT display, does it come with Linux on it? Of course not.
.doc files). If other colleges start creating policies like this, that might just cut down on the Microsoft-centric atmosphere.
When I first came to MIT, I knew about Windows and MS Office. That was it. Was I criticized for running Windows? Was I sneered at by zekr1t n1Nj@ Haxxor dudez who were running Linux or NetBSD? No. Instead, someone suggested (nicely; not by saying "Try running a _real_ OS") that I give Linux a try - If I didn't like it, I didn't have to boot into it, and I would only have lost 300MB of hard drive space (those were the days). I was given a RedHat 4.0 network boot disk and the IP address of an NFS server, and I installed Linux. My friends were willing to help me learn things, and give me pointers. There is a community mailing list that people who use Linux can subscribe to and get their questions answered by other members of the community who've been using Linux for much longer. The people on this list didn't get annoyed or flame if you asked dumb questions, nor did they gve you snide "MS sux" remarks if you inquired how to mount a Windows partition in Linux. Because of that environment, I am now a competent Linux user, administrator, and halfway decent developer. You can't expect students to rise to that level if you only offer criticism.
And can you blame students for using MS Office formats to exchange files? The media rarely mentions Linux without saying "hackers" and "computer crime" in the same sentence. Ignorant website developers and system adminsitrators think Microsoft Office is the only answer. I've even encountered people here at MIT who refuse to accept PDF documents, saying that they don't want to deal with the extra effort required to open them. (Who hasn't heard of Acrobat Reader?) In order for this bias to change, colleges need to foster an environment in which Microsoft Office is not the only format for exhanging documents. The campus computing environment here runs on a variety of platforms, including Solaris, IRIX, and Linux, so by default all course-related documents have to be in a format accessible from all platforms. This is accepted for the most part, and materials appear in HTML, PDF, and PostScript (though StarOffice has given some people an excuse to distribute
Education is a key point in this topic, and colleges are a good place to start. I would venture to say that the majority of college students who only use Windows do so not because of choice, but because they are unaware of the alternatives, or because the alternatives seem daunting and unnecessary. These perceptions have to change before more college students will start using Linux.
There is no sig, there is only Zuul.
I would disagree. Computer science is about application of principles, but programming tends to not be. CS tells us what P and NP and P-space and the rest of the goddamned classes in the pyramid are, it lets us quantify how long a quicksort runs on average, why trees are handy and why they work at all, what we can and can't compute (Turing's Halting Problem) and what qualifies intelligence (the Chinese Room problem in AI research). CS takes the theories and concepts that underlie implementation, and can be broken down into its fundamental laws.
Programming, on the other hand, at least as I see it, has a lot to do with technical anecdotes. For example, in C, typedef'ing a struct with the tag underscored, so that you can type just "link" instead of "struct _link" every time you touch a node in a linked list. Or, writing a fuzzy routine that decides whether to inline or outline the clause of an if function in a compiler, or knowing that NVidia cards have funky OpenGL fog processing under certain driver versions, and that under Windows you have to manually notify child windows of font changes. Computer Science is a pure science - Programming is more akin to engineering and applications of pure science in the real world. x86 is an application of a Von Neumann architecture, the Haskell language is an application of higher-order functions.
Good computer scientists can be good programmers, but aren't necessarily. I number many CS degree holders among my colleagues and friends who can't hack their way out of a paper bag. At the same time, I know many who can.
You are right and wrong on one account though: I couldn't program my way out of a paper bag because I WAS learning how to solve real problems. Most of the stuff I did was all theory and enough programming to illustrate it. Did I master C? Not really, but enough to solve problems in my OS class. Did I talk about Lisp in my sleep? No, but I knew enough to create a variation on battleship for my AI class. Is ORCA useful for anything nonacademic or does anyone actually use the Amoeba distriubted OS? No, but it taught me to think that way. My Computer Science degree was just that: Computer SCIENCE. I've had enough of a problem solving background to figure out a way to do almost anything I put my mind to, including installing, running and progrmming for Linux. I'd rather hire someone who thinks about a problem first and then applies what they know to it, including where to look if they don't know the answer.
Lastly, it's been my experience that at most computer labs the staff has been the more clueless than those asking the questions.
psxndc
The emacs religion: to be saved, control excess.
Sigh. My point is that an awful lot of companies, and even more individuals think that tech support will solve all their problems for them. That, my friend, is clueless. This attitude is based solely on accountability. Many people who are In IT For The Money (MCSEs, management, etc.) can't take responsibility if things don't work. What do they do? They use tech support as a scapegoat. And the companies that provide said support typically have very little capability to do so. It's there for the illusion of reliability. Ask some people who have dealt with microsoft support how many times the solution is "reboot, if that doesn't work do a reinstall". These clueless companies can't rely on usenet or irc because the management won't accept "sorry, things aren't working and I did what some anonymous dude on IRC said to do" as much as they will accept "sorry, things aren't working and I did what Jack Schmeckler, senior Microsoft Tech Support Weenie, said." In both cases you're just as fucked because things aren't working. Yet somehow, if you pay for support and don't get a solution it's ok...even though often you get far superior support from the geeks on irc and usenet. That is my point.
And FYI I couldn't care less about linux becoming mainstream. Yeah you heard me. Fuck mainstream linux, it blows. I've been a user since the days when all you had were a boot and a root floppy, and everything else was do it yerself. I like it like that. When you have mainstream you cater to the intelligence of the average person. That leads to things like microsoft's glorious products. And all this "it's the desktop os of choice...for the masses!" bullshit has been creeping into linux distros too. Have you seen the stuff they have on new "mainstream" linux distros? Yeah they work out of the box with a cutesy x installers and all this other cruft, but god damn if it isn't more trouble in the long run than burning a minimal copy of debian and building the software you need, as you need it.