kotlinx-cli VS kotlinx.coroutines

In Kotlin, I've been having a great time with kotlinx-cli. No macros involved or magic involved, and it's closer to the author's own ideals.

(And some less good ones https://github.com/Kotlin/kotlinx-cli, despite being official)

Not exactly sure what you're doing, but check out https://github.com/Kotlin/kotlinx-cli which is an official multiplatform solution for parsing incoming options. If you can use it in your case, great! If not, you might at least be inspired by the API (and how extensive even a "simple" idea can get).

For CLI programs in Kotlin, I suggest taking a look at kotlinx-cli or, especially, Clikt, for idiomatic Kotlin code without annotations and such. Of course, after having already written the program, you're most likely not gonna switch that out, but I just wanted to inform you about that.

What about the official command line parser from jetbrains? https://github.com/Kotlin/kotlinx-cli

I think, you can use libs for that. ex: Clikt, kotlinx.cli, picocli

Nice work! Welcome to Kotlin, it’s quickly becoming my favourite language. (Former PHP, current Java dev here). You should check out https://github.com/Kotlin/kotlinx-cli if you want to take it to the next level.

There is https://github.com/Kotlin/kotlinx-cli but you'll have to weigh this against quality and completeness of third party efforts as you've already discovered (in any case you'll probably need multiple libraries).

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.