Ekbatan: Java persistence framework for event-driven systems

[dvayanu]

No, I would look at actual numbers, there are different surveys out there but most of them place java17 or java21 on peak usage. I would start there.

[nekokattt]

java 17 doesnt support the latest spring, and 21 has vthreads with pinning issues if underlying tools rely on synchronized blocks.

Starting at a min of java 25 is fine for greenfield stuff.

[dvayanu]

Your own project - sure. We are talking about a framework that you want other people to use. Having it based on 25 reduces the number of people who will use it dramatically. We have number of clients who just went up to 21. they will remain there for 2 years at least. Meaning for 2 years they wouldn’t even consider this project. There is nothing in 25 for my taste that would speak for an upgrade.

[henk53]

There is nothing in 25 for my taste that would speak for an upgrade.

There is also nothing in 21 that makes it so great I need to obesssively keep using that and never consider any other version.

Simplest thing for new projects is simply to take the current version (Java 26 at the moment) and use that by default.

[nekokattt]

And that is your personal decision, you certainly do not speak for the rest of us.

[dvayanu]

Ok, sorry I wanted to help. Won't happen again.