kotlin-flow-extensions VS kotlinx.coroutines

I don't know, why I'm downvoted here, but it is very relevant if the library provide the operators you need or if you have to implement them yourself. If Kotlin Flow is enough, then use it. From experience you don't have to go to far to miss operators from Reactor or RxJava. Maybe some day additional libraries like https://github.com/akarnokd/kotlin-flow-extensions will fill the gap, but for the time being Reactor or RxJava offer a lot more for (not trivial) real world use cases.

Why do you want to keep Flow such a small library? It could be an attractive alternative to RxJava or Reactor, but it misses many useful operators today. On the other hand it brings a lot more operatores than would be required as a foundation for other frameworks (likeKotlin Flow Extensions). From my point of view Flow stays in the middleground with no good reason.

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.