You are correct. Still a student. I'd appreciate some of your insights though as you seem to dismiss my point.

Anyway I did make some actual experience in a year project (in Java) with 13 people. Some were especially unexperienced. C would have *definitely* been the wrong language here. We still had many strange bugs (that triggered only occasionally and seemingly random) that were - among other things - due to mistakes like off-by-one errors in loops that could have been easily avoided (because some team members didn't use for-each loops).

I can only imagine the debugging horrors if we had used C and had to debug buffer overruns that corrupt data structures and trigger all sorts of crazy behavior. Java complaining about out-of-bounds access is a good thing (if you are not working on systems software).