Slashdot Mirror
Are Colleges Helping to Maintain the Microsoft Monopoly?
lexus99 asks: "Recently, while attending college and wanting to take tests in order to avoid taking basic computer courses, I have signed up for a few SAM (Skills Assessment Manager) tests. What really surprised me is that these tests are entirely based upon Microsoft products (Windows XP and Office XP). Note that this course is -required- before taking any any of the more advanced courses. Is this not a clear cut case of U.S. Colleges forcing its students to exclusively use Microsoft's software? Does Microsoft pay for this 'privledge', or do the schools get some type of M$ discounts? I don't believe that I will have any problem passing these tests, as I frequently use M$ software in my workplace, but I cannot help but feel insulted that I have to take them in order to take more advanced UNIX courses." This issue is a lot more complex than it sounds. Many colleges fall into Microsoft's software because they do get decent volume discounts and Microsoft provides them with decent service, so why change what works? However, with the new licensing schemes that Microsoft is beginning to push, maybe we'll see some change in this area in the near future. Have any of you seen evidence of Microsoft worming it's way into your college courses?
This is not a troll ... I use Linux/FreeBSD exclusively; don't even own a Windoze box ... BUT ;), but this is the real world. (Unfortunately, IMHO), windows is what is "out there", predominantly. While I am excited by the growth in Linux's market share, and anticipate the day MS is no longer an effective monopoly, I am realistic; One needs a minimal level of proficiency in MS Products to succeed. At work, we are a GNU Linux/FreeBSD shop; all servers, all development,EXCEPT for the workstations in Sales, which are Win2000 ... So, even though I am a "Unix Guy", I still have to deal with Windows, which is the case in, I suspect, virtually any job (hell, even if you are a web developer in a strictly Unix Server environment, you STILL should test on Windows browsers!!)
... What exactly is your problem here? do you think you should be graduated ignorant of the OS with the *vastly* greater market share? What would *that* say about your school?
1) requiring students to have a proficiency in MS Products in no way "forcing its students to exclusively use Microsoft's software?" The problem here is your [mis]use of the word "exclusively".
2) I am as pro OSS as anyone (except perhaps RMS
So
Universities have been promoting Unix for many years and prior to Linux were probably the single most important factor keeping it alive.
Just as Unix and its derivatives have played a prominent role in industry on the server, MS OS's obviously have played a prominent role on the desktop. If a university wants to prepare students for the real world, it needs to include all the most important OS's, languages, etc. Instructors should point out the strengths and weaknesses of each and let the students draw their own conclusions.
Any "Educator" who teaches a programming classes and requires a specific compiler is an incompetent idiot and you should not believe a word he says.
I'm not sure I care for your tone, and I certainly don't agree with what you have to say.
Can we agree, for sake of discussion, that it's impossible to teach a programming language without letting the students get in there and program with it? I mean, you can read K&R from start to finish as many times as you like, but you need practical experience writing programs, screwing them up, and fixing them to really understand the language.
So in order to learn, students have to program. And, obviously, their efforts have to be evaluated by the teacher, right? So it's not just a student sitting at his desk writing programs, and compiling and running them, all by himself. There's a feedback loop, and the teacher is an important part of it.
Students in an introductory class are there to learn a language, or an API, or a set of basic concepts. They're not there to learn how to use a particular editor, or compiler, or debugger. The tools they need to use are just... necessary evils, I guess. You can't compile without a compiler, but using the compiler is secondary to your purpose. So the tools-- the editor, compiler, debugger-- should get in the way as little as possible. If you're thinking about how to use the tool, you're not thinking about what you're really there to learn.
The same goes for the teacher. Nobody can be expert in every editor, every compiler, every debugger. If a student has a problem with one of his tools, the teacher needs to be able to get in there, solve the problem quickly, and get the student back on track. In order to do that, the teacher needs to be an expert on the tools used by the students, so he can spend as little time on them as possible.
You see, I think I disagree with you completely. A teacher is responsible for creating an environment in which students can learn what they came to learn, and a good teacher will do what it takes to make that happen. If that means telling the students to write their programs with Visual C++, then good for him.
So, in conclusion, I think the truth is almost the complete opposite of what you said. I think any educator who teaches a programming class and doesn't require each student to use the same compiler and platform probably isn't making a good enough effort to keep the students focused on the material at hand.
I write in my journal
The only computer science classes you're going to get on Windows at Carnegie Mellon University is if you're a non-CS major taking intro CS classes. These are done using Metrowerks' suite (as opposed to MS's).
Everything else is done on Linux or Solaris. I'm taking a *video games* course that is taught on Linux.
Couldn't be a better place if you like doing your work in a UNIX environment.
Students are told in their third CS course that while they can turn in proofs written in Microsoft Equation Editor, that it will be harder, and that they are strongly recommended to learn LaTeX.
I still remember a philosophy professor that handed out an assignment in Word format.
I thought about complaining, but thought that it wasn't worth it, so I just printed it out at one of the clusters that have Windows installed.
The next day, in class, the professor said "due to overwhelming demand, future assignments will be given in PDF format..."
There's no reliance within the university on Microsoft file formats, and serious animosity to moving to anything that's available only from Microsoft.
If you want a good CS curriculum that isn't a bunch of regurgitated "how to design foo in Visual Studio", and you like UNIX...you're likely to like CMU.
May we never see th
Thanks to Balmer and our good Linux-friendly friend news.com, we have more wonderful Microsoft quotes.
.Net is obviously XML): Well, the benefit of .Net is XML...We take the XML connection and we extended it across both client and server -- while other guys are only server-focused. It's about connecting people to people, people to information, businesses to businesses, businesses to information, and so on. That is the benefit....it's a set of code we ship that...people use to help build applications that process XML information....it's getting to be conventional wisdom that the future of IT is around XML. But I'd like conventional wisdom to be that XML brings benefits today, and the best way to participate in the XML revolution -- in terms of user benefits and productivity -- is Visual Studio.Net.
...next major Windows release, called Longhorn. I'm sure we will have some service packs in between.
Balmer Quote 1: The truth is, we probably made (.Net) a little harder to understand than we (should) have.
Balmer Quote 2 (in which Balmer makes it quite plain that he's going to drive home the point that the marketroids prepped him with -- that XML is Good, money should be spent on XML, and
Balmer Quote 3 (in which Balmer shows himself happily living in his own world): A Yankee Group study says 40 percent of corporations surveyed were looking at operating system alternatives such as Linux, in part because of the Microsoft licensing program. But I think they are okay with where they are.
Balmer Quote 4: The Linux [platform] hardly runs any applications, except a bunch of shareware stuff that's not very good.
Balmer Quote 5: There has yet to be any innovation, new features or new capabilities out of the Linux platform. [Me -- so how the hell has *Microsoft* pushed technology forward?] But I don't think anyone should expect anything innovative coming out of that [Linux] world.
Balmer Quote 6: And we are going to have as or more a community as Linux does. [Me -- in your wet dreams, Balmer]
Balmer Quote 7 (in which Balmer discusses the buggy nature of Windows):
May we never see th
I just recently graduated from the Comp Sci department at SFU. My impression: The business faculty is very pro-Microsoft. Everything is done using Word, PPT, IE, etc. The problem is that the people making the decisions have gained their skills on MS platforms.
A good chunk (probably about 2/3) of the professors in the Comp Sci department despise MS products and are *nix guys. In other terms, prefer to use *nix on their primary machine. But, and a big but, a lot of stuff that is taught that is platform specific, is taught with respect to MS products. For example, GUI development is taught using MFC.
And that is the problem. When general computing methodolgies/techniques are taught, they apply to *nix platforms without much tinkering. But when you try to apply techniques to MS platforms, there is a poop-load of exceptions that you have to be aware of.
For example:
This how you code in C++, but this is how VC++ implements for-scoping.
These are the techniques to design "good" user interfaces, but this is how you would implement them in Windows.
There is a lot of pressure from industry for students to learn to be efficient on the Windows platform and other "high demand" tools/methodoligies (such as Java/extreme programming/XML/etc). What usually happens is that companies screen based on "buzz words". And there is a lot of pressure from industry to produce graduates that have training in licking the flavour of the month, rather than having solid understanding of Comp Sci principles. They seem to want MCSEs, that can get the particular task done now and do not care about the future; rather than people who understand general principles that will apply for decades to come.
For example, a local Vancouver company [cough]Crystal Decisions[/cough] did not want to hire me for a position because I had not programmed in Java. Despite the fact that I have been writing Object-Oriented C++ code for 5+ years and that I'm currently teaching my sister Java who is taking CS101.
The problem is that CS departments are very heavily influenced by industry. And who is the biggest heavy-weight in industry? (That question was rhetorical).
I'll not dwell too long on this; Your analogy to Esperanto is flawed. Mozilla speak's the Queen's HTML/CSS/DOM/etc, while IE speaks a slang popularlized by MTV & friends. Those who understand the slang might not understand all your fancy words or be confused when you respond positively to a double negative, but you're speaking pure English.
I see you don't claim to be a web designer. A casual speaker of English wouldn't care at the misuse of a semicolon. A professional writer wishing to write to a casual audience might curse that he can't convey the exact meaning a semicolon would bring, because the causal audience wouldn't pick up on it. So he curses and writes longer sentences that everyone will grasp.
Web designers writing for the causal, apathetic, audience have to write so that IE understands. IE is the 7th-grade English level that novels need to be written for. IE doesn't understand what a comma splice is, but it understands "UR K-KOOL DUDE", even though "UR" should be "U R".
I see many pages that IE renders blatantly wrongly, but then, like most web designers, I've usually written those pages: The next 75% of my job is getting IE to display it the way my other 7-10 browsers do. Successful web designs are done this way because it is impossible to start with an IE-specific design and go to a design everyone can use.
Your last paragraph is curious. The standards are set, and people build implimentations off those standards. Because I impliment the standard in a sub-par way, but I market well, should the quality of the standard be lowered and invalidate the work of dozens of higher quality projects?
It has been a long time since I saw a web site Mozilla does not render properly, by the way. css/edge is one I usually point out when arguing for standards acceptance. These designs are beautiful and elegant, but fail in IE and old versions of Opera. These are simple things. This copy of the OGF's SRD demonstrates one of the simpler things IE just can't grasp.
Anyhow, I understand your run-with-mob perspective, but I don't believe it can apply rationally in this case. It's a quick step to communication lockdown if we allow our method of communication to be controlled entirely by a single corporate entity, whoever the hell they are.
I'm as mimsy as the next borogove but your mome raths are completely outgrabe.
Well, you shouldn't teach to a product, but when it comes time to do the assignment, and there are only 1 or 2 TAs, busy with their own classes/research, it's far easier to grade upwards of 100 assignments if you don't have to try and find 7 types of computers/compilers to grade.
:)
At Northwestern, we alternate between needing Visual Studio and Linux, and I personally do all my dev on OS X and then take an hour to make sure it runs on whatever platform I need. It's worked fine the past 3 years
Josh
There are really two important questions here:
The first question seems to about whether colleges are getting people comfortable with Microsoft products, or accomodating them if they are already comfortable. OTOH, the second question is a matter of whether courses specifically teach skills in a Microsoft-centric fashion.
Realistically, I can't speak to a trend, but I can tell you how things are at my school. I attend an engineering college. Obviously, this makes us not big on CS; therefore, we tend to deploy Windows on most of our open labs. It's what most students and professors are comfortable with when they arrive. Therefore, a lot of non-CS students see a lot of Windows. At least at first.
But simultaneously there is an open Linux lab in which anyone can get accounts with non-too-shabby computers. Almost no one but Geophysics uses it, but they require its use for some courses. And all of the nice physics labs for 3rd year and higher physics majors run Redhat. They're set up with Linux because all junior level and above reports must be done in LaTeX.
Everyone is required to take at least one programming course, which normally winds up being Fortran or C/C++ for everyone. Chemical engineers can take VB. C/C++ is taught almost exclusively on IRIX boxes. Only recently have we had a teacher that even required any exposure to visual studio for that class -- or any low-to-mid level CS class.
As far as CS students go, all high-level CS classes tend to either be a Unix-environment or a 'use any environment available on campus'. Most teaching is mathematically and theoretically centered. I can't count how many times teachers have said in lecture that we're being taught important theory and not too much application because we might as well go to a trade school if we just want to learn current applications.
What about non-CS required courses? We're all required to take a lot of general courses, one of which (EPICS) includes required use of Microsoft Project. We're all required to take a year of calculus-based physics whose labs were taught in additional Redhat labs. They're not Windows labs.
Myself, I find this pretty mixed. There are a lot of *nix machines on campus but they're frequently not obvious until you get in a class that requires them or you simply seek them out. We more-or-less force some cross-platform experience on all majors. But if someone wants to be all Microsoft, he can probably get by like that if he doesn't mind taking alternate courses and debating with his counselor. And the same can be done for someone who wants to go all Linux.
My experience is, despite heavy Microsoft pressure, we're a rather OS-balanced school. I can only hope all schools are along the same lines.
Oh, and how do I know we have heavy Microsoft pressure?
Just a hunch.
You like splinters in your crotch? -Jon Caldara