As long as coroutines are experimental i would not...

# coroutines

[kioba]

As long as coroutines are experimental i would not recommend. But If youchose to go with coroutines without rx i would love to hear about the experience and you should definately write a blog about it 🙂

[deviant]

experimental doesn't mean alpha https://stackoverflow.com/questions/46240236/can-experimental-kotlin-coroutines-be-used-in-production?rq=1

[kioba]

I did not want to disscorouge you, i just shared my concerns 🙂 but anyway thanks for the link!

[julienviet]

my opinion is that coroutines allows you to reason about asynchronous code in a synchronous manner, likewise JMM allows you to reason about java memory model

[julienviet]

for some case it is interesting

[julienviet]

for instance the classic database acquire/use/release connection

[julienviet]

I find it much more natural using the try/catch/finally construct than with Rx

[julienviet]

writing a non blocking parser also is an interesting case: if you have ever written a parser, you find it much more natural to reason about parser in a synchronous manner than in an non blocking manner

[julienviet]

both are state machines

[julienviet]

but with coroutines for me it’s easier to reason about it

[julienviet]

here is an example of an HTTP parser

[julienviet]

written with vertx and coroutines

[julienviet]

https://github.com/vert-x3/vertx-lang-kotlin/blob/master/vertx-lang-kotlin-coroutines/src/main/kotlin/example/Example.kt#L203

[julienviet]

you can compare it to the Netty HttpRequestDecoder

[julienviet]

(which is much more complex and complete of course that’s an example)