My god. It's truly amazing how any technical or academic topic seems to degenerate into a Java vs C debate. Is there a law for that?

I think the "Java <-> C"-debate is an instance of the problem "Should studying computer science be mindwreckingly hard or should studying computer science make you able to program things?". Plus, you can also bash Java in this special instance, which is always nice coughs.

Other instances include "Compiler construction or not?", "Theoretical computer science or not?", "Assembler or not?".

That would hold up if learning a bit of memory management was actually "mindwreckingly hard".

And then you had to debug something which resulted from corrupted pointers into the stack, partially being still good data and partially being nonsense.

After reading the first sentence of said post, I actually thought he was trying to criticize Java.

>I think the "Java <-> C"-debate is an instance of the problem "Should studying computer science be mindwreckingly hard or should studying computer science make you able to program things?".

Your wording is heavily loaded. In any case, learning computer science should absolutely not be about learning to program.