Re:The 'Anti-Java' Professor and the Jobless Programmers
by jrockway on Tuesday July 29, 2008 @10:38PM
(#261405)
spend more time on design/making and fixing higher-level issues
Of course, there are "higher-level issues" that you can't express in Java. Java convinces students (and professors, sadly) that the only kind of OO is single-inheritance with interfaces and no MOP. Java convinces students that programming is all about making the not-really-static types match. I won't even mention what a hack functional programming is in Java (and I'm sure most students never even hear how to hack in FP to Java). Checked exceptions were widely considered a huge failure. Honestly, I think most of the time you'll spend with Java is going to be time spent working around its retarded limitations. Do we really want to teach kids that programming is about dealing with limitations in your tools?
At the very least, limiting yourself to Java limits your ability to learn programming. Java isn't a very good language. It is missing features that were widely considered "a good thing" 20 years before its invention. Note that I don't care about teaching memory allocation and freeing the memory, that's monkey work, not computer science. So I'm not advocating teaching C. But languages like Lisp will let you teach all the computer science without workarounds, and still have all the "safety" of Java. (Plus, Lisp programmers get paid a lot more than Java programmers. Surely that's a selling point?)
Of course, there are "higher-level issues" that you can't express in Java. Java convinces students (and professors, sadly) that the only kind of OO is single-inheritance with interfaces and no MOP. Java convinces students that programming is all about making the not-really-static types match. I won't even mention what a hack functional programming is in Java (and I'm sure most students never even hear how to hack in FP to Java). Checked exceptions were widely considered a huge failure. Honestly, I think most of the time you'll spend with Java is going to be time spent working around its retarded limitations. Do we really want to teach kids that programming is about dealing with limitations in your tools?
At the very least, limiting yourself to Java limits your ability to learn programming. Java isn't a very good language. It is missing features that were widely considered "a good thing" 20 years before its invention. Note that I don't care about teaching memory allocation and freeing the memory, that's monkey work, not computer science. So I'm not advocating teaching C. But languages like Lisp will let you teach all the computer science without workarounds, and still have all the "safety" of Java. (Plus, Lisp programmers get paid a lot more than Java programmers. Surely that's a selling point?)