I was reading through a rather old forum post about jvm languages; it seemed most people were interested in a better Java with nice performance characteristics and a little less boiler plate. Without further ado, I present to you http://www.eclipse.org/xtend/
I think this language is very nice especially if you just want a coffee script for Java.
In my opinon, removin “boilerplate code” makes it easier/quicker to write things, but harder to debug and understand.
So instead of instructing the VM of What to do, you have to Guess what it will do.
I rather give write the code with specific intructions what objecttypes to use, return and what parameters (classtype) a function has to accept.
When looking at a function from another dev, wich has quite bad variable names, its much harder to find out what it can actually operate on.
Just add lambdas, operator overloading, multiple extends to Java and I will be happy. 
Did either of you take a gander at xtend? Xtend is not so concise that it looks like pure mathematical symbol puke, however, it does cut out some “ancillary” extras that come from the Java language. I thought you fellas might like it(I sound like a salesman lol). What I really like about it is that if you use eclipse its an easy swap with Java and it works seamlessly with Java code(I really mean that this is not some Scala advertisement) since it compiles to Java code and not to bytecode(which you can look at, it maintains an eclipse folder with all the transpiled code right in front of your face).
Lol, yea. The only reason I used J++ is because I saw someone else in this forum use that to describe the “next” Java. Although, I do not know why they would and, in retrospect, I have no idea why I titled my thread that way. Java is supposed to be a gain over c++, so labeling a more advanced Java as a language closer to the machine was the wrong title.
There is nothing wrong with using this addon, if you feel more productive with it.
Thanks for pointing to this project anyway.
oh nice. now i can implement some operators for vecmath. the way all the arithmetic methods change the value of the object instead of returning a new one is completely screwy.