Comment Re:Communicate first? (Score 1) 662
Grad Student Invents Cheap Laser Cutter 137
Optimus Prime Made of Junk Cars In China 43
First Halophile Potatoes Harvested 117
Activision Wants Consoles To Be Replaced By PCs 344
Prince Says Internet Is Over 450
Project Natal Pricing and Release Date Revealed 156
Doctors Seeing a Rise In "Google-itis" 368
Comment Re:So what? (Score 1) 663
Cheap Cancer Drug Finally Tested In Humans 363
Comment Re:So what? (Score 5, Insightful) 663
What's the big deal? One programming language is like the other, at least within the same paradigm. If you can program in Pascal, you can program in C. If you can't you learned a syntax and not "how to program". Basically, when I was a computer science student, we got one language taught for the concepts and the rest was just "swim or sink". That's the way it should be. I really have a problem with programmers who have problems switching from their preferred-language to another because it's unfamiliar. Well, no, it's not... It's the damned same thing with diverging syntax.
Basically, the premise of the Exam Board is quite right: the goal of programming is to have problem solving skills. Whatever language conveys that is completely uninteresting to me.
Oh, and just for the record: programming is just a small part of the computer science curriculum... or at least it should be.
There's a lot more that goes along with a language
Sure, if you know how to code OO, use iterators, understand switch statements and other language-related elements you can change languages and write an algorithm or two
But
Do I know best practice for everything?
If I'm a c# programmer. Do I know important differences between Ruby 1.7, 1.8. 1.9?
Do I know what the best inversion of control framework is? Or what the best ORM to use is? Am I familiar with how to use it?
If I'm a Ruby developer am I aware that in a