Vladymyr L Well, because with callbacks I more or less understand how it works. With some kind of run loop, queue of tasks and stuff like that. And I can understand why and when something is executed. But with more involved techniques it becomes really hard to track it, to debug it, to read the code, to understand stack traces...
![Gunna - HIM ALL ALONG [Official Visualizer]](http://i.ytimg.com/vi/HiCxoDeo0hc/mqdefault.jpg)
by far the best technique of managing asynchronous code so far
Is there an example we can see for writing/using higher-order functions with Coroutines?
You say callbacks are hell? No way! Understanding how coroutines or async/await stuff works is real hell! 🤯🤯🤯
Why? The async/await works most of the time in predictable way, while callback always include something new!
Vladymyr L Well, because with callbacks I more or less understand how it works. With some kind of run loop, queue of tasks and stuff like that. And I can understand why and when something is executed. But with more involved techniques it becomes really hard to track it, to debug it, to read the code, to understand stack traces...
right...
@@alxkub it looks like gap in your knowledge. Imho
You will eventually catch up with programming. I had been in same place but eventually you will understand why these libs and all are there.