netty-incubator-transport-io_uring VS kotlinx.coroutines

- For network I/O, Netty as an incubating transport that is promising [1].

- For disk I/O, JDK's Loom project [2] has mentioned its plan to rely on io_uring on Linux [3], but there's no ETA AFAIK.

[1] https://github.com/netty/netty-incubator-transport-io_uring

Yes, I think io_uring is slowly making its way onto Java ecosystem. Example: https://github.com/netty/netty-incubator-transport-io_uring

I guess it will go into the JVM too.

Maybe maybe not. If you want to take advantage of things like io_uring you're going to be doing that with a JNI lib. Such as this Netty incubator support for it https://github.com/netty/netty-incubator-transport-io_uring

There is a Java library from Netty which has implemented io_uring and could be borrowed.

Now, let's consider an example. For instance, let's create a Kotlin/JVM project with kotlinx.coroutines library as a dependency.

Greetings community, I just submited a PR to Kotlin coroutines with two additional operators :

The harder parts of Kotlin are going to be things like kotlinx.coroutines, but that's just a library, not a core part of the language. It's about as hard to learn as a comparable library in another language, like the Task Parallel Library in .NET.

Kotlin has coroutines that are supported by the language and implemented by a library (the implementation remains platform-dependent): kotlinx.coroutines and a sandbox environment is available here to try it out.

That said, since it seems like you're doing UI stuff (Android?), you're best off doing all of the UI code in coroutines, using Dispatchers.Main as a context (as provided by one of the platform-specific coroutine libraries), since this will guarantee that your UI code will be safely run in the UI thread.