Java 21

[calum-maclean-ul]

With the change to Java 21, it means that it is no longer possible to use asn1bean with any version of Java before Java 21 (e.g. Java 8, Java 17).

Was there any particular reason why the move to Java 21 was required? Are some Java 21 features now required in order for you to develop and build asn1bean?

[calum-maclean-ul]

Hi Stefan
Any update on this?
Calum

[sfeuerhahn]

Hi Calum,
I updated the gradle version which required a newer version of Java to execute the build. So I took the chance to upgrade Java so that future version can use the newer Java features. Also Java 8 is extremely old. Is it a problem for you to upgrade to a newer Java version?

[calum-maclean-ul]

Thanks for getting back to me.

We currently use an older version of Java. It's our plan to update to a newer version, but this isn't always straightforward in practice - this will be the same for many organisations.
We don't currently have a need to update to a newer version of asn1bean, but we like to keep the option open.

https://lp.jetbrains.com/the-state-of-java-2025/: the latest Jetbrains survey indicates that 40% of developers use Java 21. So this means that around 60% use earlier versions of Java.
Java 17 developers (39%) and Java 8 developers (31%) will not be able to use asn1bean.
(Note that the numbers add up to more that 100%, presumably because people use more than one version of Java.)

As a library developer, if you use a newer version of Java, then some people will not be able to use your library (according to the stats above, this is around 60%).
If you use an older version, then more people will be able to use your library, but you won't be able to use the newer features of Java.
So the choice of which version of Java to use is a trade-off.

Ultimately, it's your prerogative as the developer of the library. But it's useful to be aware of and consider the implications and trade-offs, as I described above.