Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FFM / JExtract #14

Open
StevenCurran opened this issue Apr 12, 2023 · 2 comments
Open

FFM / JExtract #14

StevenCurran opened this issue Apr 12, 2023 · 2 comments

Comments

@StevenCurran
Copy link

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.

@StevenCurran StevenCurran changed the title FFM / Jextract FFM / JExtract Apr 12, 2023
@bbeaupain
Copy link
Owner

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!

@siy
Copy link

siy commented Nov 18, 2023

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants