Oracle talked about Java 7 at the first stop of the Java Road Trip. The main speaker was Brian Goetz, author of Java Concurrency In Practice.

Despite the disclaimer that everything including syntax is subject to change, the talk was pretty interesting.  Here are my notes.  (this was largely written on my iPad; please excuse any typos)

Modularity

• The JRE download is 13mb, but most code doesn’t get run by ordinary apps
• The monolithic jdk makes new releases of platform take longer to roll out
• Modularizing apps helps with jar hell and finding out at runtime that something is missing/wrong
• Will provide mechanism for apps to express dependencies in way useful to both humans and tools
• Based on concepts in Maven and OSGI
• Current draft has: Module-info.java defining module and version number along with what module and versions or ranges you depend on
• Classpath will be legacy mode, preferred mode will be to turn your app into a module

Multi lingual support

• JVM is a managed code environment
• Scala is a lot like java, but other dynamic languages (like Ruby) run slower because need to rely on reflection or code generation.
• JVM is more like Smalltalk than like Java , but some places is tied to Java
• Da Vinci machine project is targeted to adding features to better support dynamic languages. In particular dynamic method linkage which is being able to select version of method based on type of arguments
• Invokedynamic vs invokevirtual for method selection and linking. Once calls stabilize, don’t look up in vm anymore, then inlines and is as fast as in  java.  This is a goal, need to get there.

Productivity

• Project coin – add half a dozen small language changes to simplify everyday tasks.  Would be at  level of enhanced for loop

1. Reduce boilerplate of generics with the the diamond operator (not really an operator)

   Map<String, String> map  = new HashMap<>();

2. Better numerical literals to make long numbers more readable.  Similarly for binary (long string of 0’s and 1’s)

   long cc= 123_5678_567;

3. Collection literals – declare inline like we do with arrays and hard coded data.  More declarative. Like associative array in Perl, but may not go that far
4. Automatically close resources in try/catch.  Better idiom

   try (InputStream in = createInputStream()){
   // code that reads in from stream goes here
   } // compiler will call close for you here

Performance

• Goal: facilitate scalability across multiple cores
• Fork join extend recursive action to split into subtasks and join to get answer.
• Will be added to concurrency utilities.
• Don’t have to tell it how many cores you have
• ParallelIntArray class automates common operations filter, map and reduce so can say what want to do declaratively

Closures

• Saving the best for last.
• Like anonymous inner classes but without boilerplate of anonymous inner classes
• Still debating syntax
• Still debating whether return type should be declared
• Still discussing how to extend interfaces (will be used to add closures for Collections).  Options are “static extension methods” like in C# where you statically “pretend there were these methods are on the class and call the static methods instead.”  Also discussing ” virtual extension methods.”  Either way the closures project will finally address the issue of api evolution

#(int x)(x*3).domorestuff()