+1 for Derek and Kyle's comments. I think it's important to keep at least one level of JVM backward compatibility. I would love to dive straight in to JDK 1.8+, but that would be at the expense of users who may have infrastructure constraints that would prevent that.
As mentioned earlier it is possible to mimick those features and APIs, and help pave the way for migration later. I'd be +1 for that approach. -Taylor > On Jan 11, 2016, at 5:56 PM, Kyle Nusbaum <[email protected]> > wrote: > > I agree with Derek. > There are still a lot of people using Java 7. However, if you could make it > sort of Java 8 compatible so that when we do move to Java 8 we can do so with > relative ease. > -- Kyle > > On Monday, January 11, 2016 4:46 PM, Derek Dagit > <[email protected]> wrote: > > > I am not sure it makes sense to move to Java 8 merely because of the > clojure->java translation, but it might be good timing so I would be OK with > it. > > -- > Derek > > > ----- Original Message ----- > From: Reza Farivar <[email protected]> > To: Dev <[email protected]> > Sent: Monday, January 11, 2016 4:40 PM > Subject: Java 8 for Storm 2.x? > > I have started work on translating the util.clj to java (STORM-1226). I see > some instances when translating the functional behavior of clojure to Java > requires code that is already part of java 8. > For instance, there are many cases where a predicate function is passed > around (e.g. in find-first). I can go ahead and implement a Predicate > interface and use that, but Java 8 has already exactly that functionality > implemented. > Would it make sense to move to Java 8 for the post-clojure branch 2.x? > --Reza > >
