Download to read offline
Uploaded byAhmed Nabil
A Journey From Callback Hell To Kotlin Coroutines
The document discusses the evolution from callback hell to Kotlin coroutines, highlighting the challenges of asynchronous programming methods like threading, callbacks, futures, and reactive extensions. It emphasizes Kotlin's coroutines as a modern solution that simplifies asynchronous code, making it easier to write, debug, and manage while being platform-independent. The author, Ahmed Nabil, shares his expertise in mobile app development and Kotlin, aiming to educate others about the benefits of using coroutines.
A Journey From Callback Hell To Kotlin Coroutines
- 1. A Journey from CallbackHell to Kotlin Coroutines Ahmed Nabil Kotlin Egypt @AhmedNMahran Sat. Jan 1 2022
- 2.
- 3. 1. Writing Codesince I was 11 2. 8+ years in Mobile App development 3. Given talks to thousands of audiences 4. Prev. Android Mentor at 1M Arab Coders. 5. Worked at Hungerstation,Codly, and others. 6. Software Tech. Lead at Vodafone (_VOIS). 7. Head of Kotlin Egypt. About Me
- 4.
- 5. 1. A modernProgramming Language. 2. Developed by Jetbrains & Open-Source community 3. Since 2010. 4. Current Stable Version is 1.6.10 (as of 31-12-2021) Kotlin
- 6. 1. Multiplatform-Mobile 2. Server-Side 3.Web Front-End 4. Android 5. WatchOS 6. Data Science 7. and more Used to Develop
- 7.
- 10. ANR ● any operation> 16ms may cause Lag ● I/O operations, long running operation ● Main thread should ONLY do UI operations
- 12.
- 13. 1.Threading 2.Callbacks 3.Futures, Promises 4.Reactive Extensions(Rx) 5.Coroutines Approaches
- 14. About Me Problem Code runningin Main thread causing Crash or Lag.
- 15. About Me Threads A programsplits itself into 2 or more running tasks
- 16. 1.Expensive 2.Not Infinite, limitedwith device capabilities 3.Not always available, (e.g. JS doesn’t have threading) 4.Hard to Error-handle and debug Threads Limitations
- 18. About Me Callbacks a functionsent as an argument to another function to be executed at certain point in time.
- 20. 1.Nested Callbacks noteasy to understand 2.Hard to Error-handle and debug Callback Limitations
- 22. About Me Futures and Promises Ipromise I’ll return at some point in the future.
- 23. 1.Nested Callbacks noteasy to understand 2.Return Type : Needs changing the models (extra steps in getting the data) 3.Hard to Error-handle and debug Limitations
- 24. About Me Rx Everything isa stream and it’s observable Needs learning new apis :(
- 25. About Me Coroutines Kotlin’s approachto work with async. code
- 26.
- 27. 1.No new apisneeded, same language used (kotlin) 2.Return type doesn’t change. 3.Write sequential code while being thread-safe 4.Lightweight, can run many of them in one thread, 5.Easy to switch between threads 6.Platform independent 7.Easy to debug and detect errors. Coroutines
- 29.
- 30. About Me Follow Me @AhmedNMahran Thanks! TwitterYoutube Linkedin Medium Github
- 31.