Decompose VS kotlinx.coroutines

Different UI technologies have their own unique features, such as DataBind for XAML (WPF/UWP/WinRT), and more and more UI technologies using Turing-complete programming languages as DSL, such as Flutter (Dart), Swift UI (Swift) and Compose (Kotlin), which can only be said to have advantages and disadvantages. But don't dismiss it out of hand. For Compose, there is a Decompose framework that helps you to separate UI code from business code.

I found this one from badoo. But it seems to be overly complicated.

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.