The Perils of Java Schools

Joel Spolsky of joelonsoftware.com has written an article titled "The Perils of Java Schools". Joel blames on Java-only schools. Well, he has a valid point. Universities shouldn't discard other lanuages when they teach computer science. Infact, JVM itself is written in native code and the OS where the JVM runs is also written in native code. And there are other places where Java is not used. But I don't understand how Java prevents programmers to do recursive proramming. Joel should make a distinction between the implementation language and the programming technique. Agreed, Java doesn't have pointers. Java has its own reason not to have pointers. But then this has lead to more productivity among the programmers. Who would want to waste his time dealing with segfaults when implementing an enterprise software that changes frequently? Java is not just in enterprise software though. It's in small devices (courtesy: JME). It's used in gaming software. Schools shouldn't be meant as a place where inefficient students are weeded out. We already have a screening system where the student candidates are weeded out and we also have exams to rank the students. Java shouldn't be a reason to blame the inefficiencies on the part of students or the schools. It's the syllabus framed by the university and the tests conducted by the schools to be blamed. But then, shouldn't the companies have proper system to weed-out the inefficient candidates?