Thanks, Andrew, and to be clear this is an obscure side environment of my main project, and I am resigned to the fact that it seems doomed because the developers of Max/MSP are choosing to respond to Apple’s deprecation of their Java 1.6 environment by entirely abandoning support for working with the Java VM. So I agree, Java 1.6 is very old now, and at some point the burden of maintaining support for it starts slowing down other important progress.
The main thrust of my Clojure development is in the latest release candidate of Clojure on the latest Oracle JVM. On Saturday, August 8, 2015 at 1:03:38 PM UTC-5, Andrew Oberstar wrote: > > [...] > I can understand James' (Elliott) desire to keep Java 6 compatibility for > platforms that are slower to adopt newer JVMs, but I hope that doesn't > become an excuse for Clojure to stay moored to the JVM's past for the > long-term. > > Andrew Oberstar > -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
