You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi there! I know you are targeting java 8 here, but any thoughts on how performance / maintainability / memory safety this would benefit if using jextract on io_uring.h alongside the new FFM changes?
Thanks a lot, really cool to see this making its way into java.
The text was updated successfully, but these errors were encountered:
I think this would be a pretty large undertaking, but overall a fantastic upgrade for the project.
As you alluded to though, limiting usage to Java 19 would eliminate a large portion of potential users and companies, which is a pretty large concern for me. I think the answer may have to be "not yet," but this will be something very important to tackle down the road once 19 becomes more common.
Still open to discussing pros and cons though. I may have strong opinions... but I try to hold them loosely!
Spring already set Java 17 as a minimum, migration to the next LTS version (Java 21) from the previous LTS version (Java 17) is rather easy, so I'd expect that Java 21 will soon be a rather common. Virtual threads extend the life of legacy enterprise apps, so there will be another channel of pressure to speedup adoption of Java 21.
Hi there! I know you are targeting java 8 here, but any thoughts on how performance / maintainability / memory safety this would benefit if using jextract on io_uring.h alongside the new FFM changes?
Thanks a lot, really cool to see this making its way into java.
The text was updated successfully, but these errors were encountered: