kotlinx-datetime VS kotlinx.coroutines

Kotlin multiplatform types often come with their own serializers. https://github.com/Kotlin/kotlinx-datetime and https://github.com/hfhbd/kotlinx-uuid do, for example.

But we do have such plans for our kotlinx-datetime library and expect to provide at least a partial solution during the course of the year

It depends, time has a complex and native bound legacy. But I bet you want this https://github.com/Kotlin/kotlinx-datetime and DateTimePeriod.

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.