On 12 December 2014 at 09:11, Sean Corfield <s...@corfield.org> wrote:
> Java 6 has been EOL for nearly two years. Java 7’s EOL is currently just > four months away. Given that Clojure 1.7 is not yet "gold" and 1.8 will > likely be a year away (based on previous releases), it seems reasonable to > plan to drop Java 6 support three years after it was EOL’d. > If there are no bugs in the replacements for the EOL'ed versions, sure. > A quarter of Clojure’s users are still working with 1.5.1 or earlier so > staying on Clojure 1.7 for a year or two after 1.8 ships doesn’t seem like > a big issue. > Except that there is at least one significant improvement (Zach Tellman's small collections) that got bumped to 1.8 in the rush to get transducers out. > I’m stunned that JetBrains don’t yet properly support Java 7 or Java 8 > These are not JetBrains' bugs, they're Oracle's. > we’ve been on Java 8 for development for ages and about half of our > production systems have been upgraded to Java 8 over the last three months. > I'm happy for you, but clearly you're not using complex Swing apps to do your development. I've had probably at least 10 users report IDE segfaults recently, switching to JDK 6 has always fixed it. My userbase is miniscule compared to the number of IntelliJ users out there (in the hundreds of thousands, and an increasing percentage of them on OSX). On a MacBook pro, Java will always use the discrete GPU instead of the integrated one, which means that I get perhaps half the battery life I should do when developing. Oracle also seem to have broken subpixel antialiasing on OSX, which previously they had only managed on Linux. These are not trivial issues, and there's no guarantee they'll be satisfactorily addressed in JDK 9 either. Don't get me wrong, I'm frustrated by this. Probably the only people more frustrated by it are JetBrains, to the extent that they're considering maintaining their own JDK. Say what you like about Apple's handling of desktop Java, at least when they finally brought a version out it worked. By the time Oracle have fixed all this they'll have taken far longer to do it than Apple ever did. What are we hoping to gain by dropping support for JDK 6? Are there later APIs we want to use in core? My understanding was that invokedynamic was a train wreck from a performance point of view in JDK 7 and was significantly re-worked in JDK 8. Unless we're planning to drop support for 7 too I don't see a big win. > Sean > > On Dec 11, 2014, at 11:31 AM, Colin Fleming <colin.mailingl...@gmail.com> > wrote: > > In a future Clojure release (post 1.7) we will drop support for Java 1.6 >> > > Please don't. That will mean that Cursive will be stuck on Clojure 1.7 > until at least Java 9, and probably later. JDK 6 is still the only > recommended JVM for running IntelliJ on the Mac due to significant bugs > which prevent many users (including me) from upgrading. All IntelliJ > plugins for the moment have to be built for Java 6 because of this. Many of > these bugs have fix versions of JDK 9 but who knows when they'll ever > actually make it in. Rumour has it that JetBrains are considering releasing > their own patched JDK because of this. > > See: > https://intellij-support.jetbrains.com/entries/27854363-IDE-doesn-t-start-after-updating-to-Mac-OS-Yosemite-or-Mavericks > > > -- > 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. > -- 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.
