We'll be going to Java 18 or 19 as a minimum for MMapDirectory using the new Panama APIs once those stabilize, right?
We could probably benefit today some from record classes, but I'm not sure how much of a hint those are to the runtime VM for optimizations or if it is entirely a source code syntactic sugar thing. On Wed, Nov 3, 2021 at 11:53 AM Robert Muir <rcm...@gmail.com> wrote: > On Wed, Nov 3, 2021 at 12:51 PM Robert Muir <rcm...@gmail.com> wrote: > > > > > > It will be released, eventually, right? In six months, a year maybe? > Then it's people like me who would be affected: we use Lucene internally > and this one dependency would push the entire stack to Java 17. I wouldn't > mind this at all if there was something super-attractive there to gain but > all the benefits of Java 17 to me at the moment lie at source-code level... > I just don't see much benefit at runtime. So I personally don't feel the > need to upgrade - this applies to Lucene, my own software and even my shell > default... > > > > Separately, but if you want to stay on old stuff, then stay on old > stuff (e.g. stay on lucene 9 with java 11). This is how people do it > with all other software. If you are happy with java 11, then you > "personally don't feel the need to upgrade" and you can just stay on > lucene 9, or lucene 8, or lucene 7, or whatever! > > But there should be a place where we can move forwards: I think the > 'main' branch is appropriate. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: dev-h...@lucene.apache.org > >
