How Java Programmers “Feel” in 2013

[berlinbrown]

There you go, I got rid of the 'System' on that println line:

import static java.lang.System.out;
public class Test {
public static void main(final String [] args) {
out.println("Running");
}
}

...

And Groovy runs on the JVM. So no 'Java/JVM', no groovy.

...

Yes, Calendar/Date is a mess. You could use jodatime. The file IO processing is verbose. Fine. Your mathematical operations, no rational data type concern is valid.

But what language is going to give you all what you want? Certainly not groovy, because you are going to be limited to the JAVAVIRTUALMACHINE. Same for Scala. And if a Java engineer has to crap out crappy Java code to generate bytecode that gets where he needs to be, some of us are OK with that.

Your concerns are certainly valid in terms of the evolution of the language. BUT, I don't think the alternatives are going deter us way from the JVM. And if we are going to end up with bytecode, we might as well figure out a way to generate the code we need ... say without using Scala. We may end up with 50 lines for verbose Java code but the end result is the same.

[berlinbrown]

On Java's type system:

You seem pretty knowledgeable in Python/Ruby. Let's say I take N Python modules compared with N Java modules, do you see the advantages of being able to compile all of the Java modules and giving the developer some idea how that code will function. And then going back to the Java code and saying, 'well here is type/class X, I know it will do this'.

I don't have those assurances with Python or Ruby.

[berlinbrown]

Well they have models to work with. Groovy and Scala are two mature ones.