Are co-routines stable to use in kotlin/jus ?

"almost stable"

lol, what does "almost stable" mean? I need this for a paid webapp, not a hobby project. 🙂

My customers are not going to be happy with "almost stable" software.

In Arrow-Kt project, is "stable" i think, because some abstractions are build on top of coroutines

"Almost stable" I read as "no breaking issues known for a good while, but still under observation"

Is that it?

@ikt https://kotlinlang.org/docs/reference/coroutines.html#experimental-status-of-coroutines

Unfortunately they don't really say anything concrete there.

@ikt

At that minute marker, Roman talks about the experimental status of coroutines

So it sounds like "experimental" means: * the compiler works fine * the API might change Is that the gist of it ?

so in particular, the "experimental" refers to API, not "correctness of output code"

and it might not work

so don’t expect it to work 100% of the tiem

but yeah

I am looking at https://kotlinlang.org/api/latest/jvm/stdlib/index.html <- Is it correct to derive that "kotlin/js has bindings for WebGL1 (I'm actually using them right now)", but Kotlin/Js does not currently have official bindings for WebGL2 ?

@ikt I'm doing Android development for a living, pushed apps made with Kotlin coroutines to production since past year, and had no issue about them. Exeprimental is about API that may change before the experimental status is dropped. Stability is on par with the rest of Kotlin otherwise, it's really top quality IMHO

They’ve actively encouraged people to use it in production

Coroutines are stable in the sense that they are production ready and shouldn't be buggy. They say its experimental because the API might change (and in that case they will provide a migration path).

In a tech talk (forgot which one) someone from Jetbrains said they regret calling it experimental because it's one of the most powerful Kotlin features (and I 100% agree with that, async/non blocking programming is much easier using coroutines than anything else).

They can just stop calling it experimental then?

like @Parcelize 🙂

guys have you been using kotlin in production ?

has there been a learning curve for it ?

Personally very little learning curve (coming from java), went trough the docs and in a couple of days I was as confortable as with Java.

And then a bit more to discover the cool collection functions, the literal-with-receivers, dsl stuff, delegation etc.

I also use java, I could say my first language

it is not really learning how make a for loop work

but mostly checking for syntax