Closures in Java 7: Not Likely
davidflanagan.com
Closures in Java 7: Not Likely
1–10 of 23 posts
Re: Closures in Java 7: Not Likely
#2That's Oracle for you.
In the end the only way for the JVM environment to advance would be if large users of the JVM push for new features until the FOSS community forks and begins patching up.
Re: Closures in Java 7: Not Likely
#3Speaking as someone whose current long-term main project is Java-based: Java's development has stalled. Go and learn Scala, Clojure, Python, Haskell, . (Note that is not to say that you need to abandon whatever Java you're working on, just that Java's pain points getting fixed looks very unlikely.)
Re: Closures in Java 7: Not Likely
#4This highlights the difference between open and open.
java is technically open source, yet the decisions are made behind closed doors without any transparency.
Re: Closures in Java 7: Not Likely
#5Speaking as someone whose current long-term main project is Java-based: Java's development has stalled. Go and learn Scala, Clojure, Python, Haskell, . (Note that is not to say that you need to abandon whatever Java you're working on, just that Java's pain points getting fixed looks very unlikely.)
Working on it. But it's the steepest learning curve since I learned to program the first time.
It almost feels as though already being able to program is actually a hindrance.
Re: Closures in Java 7: Not Likely
#6Speaking as someone whose current long-term main project is Java-based: Java's development has stalled. Go and learn Scala, Clojure, Python, Haskell, . (Note that is not to say that you need to abandon whatever Java you're working on, just that Java's pain points getting fixed looks very unlikely.)
Working on it. But it's the steepest learning curve since I learned to program the first time. It almost feels as though already being able to program is actually a hindrance.
Which? Scala, Clojure, Haskell ...?
Re: Closures in Java 7: Not Likely
#7I'm more disappointed that continuations don't appear to have made it. They're available as a patch, but actually compiling an OpenJDK with them is evidently an arcane art I haven't yet mastered.
Re: Closures in Java 7: Not Likely
#8Re: Closures in Java 7: Not Likely
#9Re: Closures in Java 7: Not Likely
#10Earlier quoted context omitted.
Which? Scala, Clojure, Haskell ...?
Clojure.
This has been my experience too. I found CL, Scheme, and Haskell pretty easy. Clojure has taken me more time. I think it's because there aren't many good books yet, and because Lisp-speaking émigrés have to learn a set of new ideas that's mostly separate from the new ideas Ruby/Python/Java users need to learn.
What specifically has been giving you trouble?