The JCP isn't just for java-the-language. JCP 'controls' the JVM as well. Let's delve into hypothetical land and say that java 8 brings a number of JVM-based improvements such as default methods and method handles. Not much of a stretch as this is actually the current JDK8 planning.
Now scala has to choose: Either stick with its current approach, which would mean scala defaults and closures are NOT compatible with lambdas, and slower as well, _or_, target newer JVMs but then you have effectively the same issue. I guess scala could give you a command line switch. But all would have to use the same switch for the same libraries - i.e. you'd have to fork all libraries if the community is split and wants both versions. ugh. Complicated stuff. -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
