+1 for Java 8. Creating a modern API using the latest Java 8 features is a key differentiating point for me. There are enough Java 7 APIs around and we should not build another Java 7 API in addition IMO. If we want to add it later as a standard to EE 8+ or Java 9 Jigsaw Java 7 looks simply weird. BTW we had a similar discussion with JSR 354 as well for quite a long time. At the end (after more than one year) we finally decided to switch to Java 8. I never regretted this decision, even not now, where we we do not get into Java 9 and stay standalone. About adoption I already know quite a few people using Java 8. Even Credit Suisse is actively thinking on adopting it rather quickly.
The API as of now compared with the same functionality built in Java 7 is about half the size! I would then argue the other way round: if enough people really want to have Java 7 support, they should perhaps fork the library and add the additional singletons, remove the @FunctionalInterface annotations, add their own implementation of Optional, extend the collection classes, provide abstract classes for the base functionalities that default methods provide for each and every SPI and API.... 2014-11-28 20:22 GMT+01:00 Romain Manni-Bucau <[email protected]>: > Le 28 nov. 2014 19:51, "John D. Ament" <[email protected]> a écrit : > > > > +1 for java 8 as the default. > > > > We don't want this brand new thing looking old because it's based on an > > older JVM. Java 8 adoption is also really up there, per[1]. > > > > I dont get the point we can support it being java 7 without too much > workaround (only will be optional afaik) > > > For components you're stuffing into app servers, it's a little harder, > > since you do have to be Java 7 compliant for EE 7 (you can go lower, but > > not higher). > > > > [1]: http://jaxenter.com/java-2-111936.html > > > > On Fri Nov 28 2014 at 12:27:40 PM Andres Almiray <[email protected]> > wrote: > > > > > AFAIK JDK8 should be the baseline as it can *force* the hand for > adoption, > > > yes, this is desired. > > > Otherwise we'll be stuck in JDK7 or even worse, JDK6. > > > > > > JDK8 also opens the door for additional design features such as > > > > > > - static methods on interfaces > > > - default methods > > > - repeatable annotations > > > - usage of Optional > > > > > > Cheers, > > > Andres > > > > > > ------------------------------------------- > > > Java Champion; Groovy Enthusiast > > > http://jroller.com/aalmiray > > > http://www.linkedin.com/in/aalmiray > > > -- > > > What goes up, must come down. Ask any system administrator. > > > There are 10 types of people in the world: Those who understand binary, > and > > > those who don't. > > > To understand recursion, we must first understand recursion. > > > > > > On Fri, Nov 28, 2014 at 6:19 PM, Romain Manni-Bucau < > [email protected] > > > > > > > wrote: > > > > > > > Hi guys, > > > > > > > > just checkouted sources and seems project targets java 8. Don't we > > > > want to support java 7 as well? Otherwise it can be a blocker for > > > > adaption I think > > > > > > > > > > > > Romain Manni-Bucau > > > > @rmannibucau > > > > http://www.tomitribe.com > > > > http://rmannibucau.wordpress.com > > > > https://github.com/rmannibucau > > > > > > > > -- *Anatole Tresch* Java Engineer & Architect, JSR Spec Lead Glärnischweg 10 CH - 8620 Wetzikon *Switzerland, Europe Zurich, GMT+1* *Twitter: @atsticks* *Blogs: **http://javaremarkables.blogspot.ch/ <http://javaremarkables.blogspot.ch/>* *Google: atsticksMobile +41-76 344 62 79*
