Hum. If that's a positive spin on Java, you can count me unimpressed. I have a side project I'm maintaining (all in) Java that I spent a weekend on about two m

Hum. If that's a positive spin on Java, you can count me unimpressed. I have a side project I'm maintaining (all in) Java that I spent a weekend on about two months ago. Frankly, it was ridiculously easy to splat out code with Eclipse (and not get anything done, but that's mostly my fault). Several fundamental issues showed up: - lack of first-class functions - lack of extensibility on extant classes - grossly mutating state - Loads and loads of code that obscured what the logic of the program was Project Lombok is a heinous hack to try to get around these issues (somewhat). So is, afaict, AOP. I think for the right project - and with ruthlessly non-generic design - Java is the right tool. Otherwise you wind up with reams of wasted paper and mental overhead grappling with the sheaf of low-entropy code you've got.