[jriddycuz]

The problem with this whole argument is that the author assumes that deterministic memory performance is completely necessary. It's certainly nice, but there are so many times when it just doesn't matter.

While I agree that Java sucks because it makes certain very common things require extreme verbosity, worrying about garbage collection isn't all that important except in systems-level programming (which isn't done in Java really), and large GUI that need tons of memory and still need responsiveness. But many people wouldn't even think to use Java in those cases anyways, so I'm not really sure what this guy's point is.

[chris_j]

Read the slides again. The author isn't concerned about deterministic memory performance. He's concerned about the fact that that you can't do RAII in Java and therefore any method that allocates resources, performs an action that could throw an exception and then deallocates the resources must wrap the action in a try...finally block. This is overly verbose and the compiler won't tell you if you forget to do it.