Wait, so replacing a call to ‘map’ with a call to ‘flatmap’ is problematic? This is just how monads work. It’s how every monad has ever worked, from promises, to lists, to streams, to optionals to incremental computations... literally thousands of monads out there, and they all work precisely this same way. You have ‘flatmap’ function which flattens your nested type within your data transformation pipeline.
![ละลาย (LALALYE) - DAOU PITTAYA ต้าห์อู๋ พิทยา [OFFICIAL MV]](http://i.ytimg.com/vi/wo6r9TgausI/mqdefault.jpg)
Thank you for this excellent talk.
00:00 Introduction
03:15 Sequential code
07:06 Threads
11:15 Request context
16:46 Exception handling
23:21 Concurrent code
27:50 Cancellation
30:39 Parallel code
33:04 Streams / Channels
36:35 Stream generation (hot and cold)
40:04 Operators
41:03 Custom operator
41:59 Backpressure
44:24 Interoperability
46:16 Coroutines or Reactive Programming?
One of the best talks from Kotlin Conf 2018. Dzieki Konrad!
Immensely informative, but watch in 1.5X speed
Wait, so replacing a call to ‘map’ with a call to ‘flatmap’ is problematic? This is just how monads work. It’s how every monad has ever worked, from promises, to lists, to streams, to optionals to incremental computations... literally thousands of monads out there, and they all work precisely this same way. You have ‘flatmap’ function which flattens your nested type within your data transformation pipeline.
Now that we have Flow, we can forget about Observable/Flux/Single/Mono. :)
Very nice and informative talk
Mano a mano!
VariAble