Roman Elizarov
medium.com/@elizarov · Personal blog · on HN since 2018
Roman Elizarov, a Kotlin language lead, writes about Kotlin coroutines and flows, structured concurrency, null handling and language design.
What HN saysCommenters cite his posts on function coloring, Kotlin flows and callbacks as authoritative explanations of how Kotlin handles asynchronous code.
19HN people shared it
3linked it in comments
28stories submitted
278story points
6 years agolast shared
2018people per year2026
Most-shared posts
- 1Null is your friend, not a mistake3 people · 10 points · first shared 2019 · 4 comments on HN
- 2Exceptions in Kotlin Flows3 people · 3 points · first shared 2019 · discussion on HN
- 3Types Are Moving to the Right2 people · 167 points · first shared 2019 · 141 comments on HN
- 4Dealing with absence of value in programming languages2 people · 7 points · first shared 2019 · discussion on HN
- 5A Tribute to Java2 people · 7 points · first shared 2018 · discussion on HN
- 6Structured Concurrency – Roman Elizarov – Medium2 people · 4 points · first shared 2018 · discussion on HN
- 7Programming Binary Search2 people · 3 points · first shared 2019 · discussion on HN
- 8Functional Programming Is on the Rise1 people · 48 points · first shared 2019 · 32 comments on HN
- 9Intentional (Software) Qualities1 people · 9 points · first shared 2019 · 2 comments on HN
- 10Deadlocks in non-hierarchical CSP1 people · 8 points · first shared 2019 · discussion on HN
- 11Why I’m not enthusiastic about Java 101 people · 4 points · first shared 2018 · 1 comments on HN
- 12Application Programming Language1 people · 2 points · first shared 2019 · discussion on HN
- 13The End of the Semicolon Era1 people · 2 points · first shared 2020 · discussion on HN
- 14Kotlin Coroutines, a deeper look1 people · 1 points · first shared 2018 · discussion on HN
- 15Simple Design of Kotlin Flow1 people · 1 points · first shared 2019 · discussion on HN
What HN people wrote when they linked it
The_rationalist · 2020-05-16
Kotlin has solved colouring before loom ->
https://medium.com/@elizarov/how-do-you-color-your-functions-a6bb423d9…
Go was the first to solve colouring but they have it seems a less type safe solution
jillesvangurp · 2019-07-23
An interesting topic related to this is co-routines in Kotlin which implements this for Kotlin. This recent article by Roman Elizarov https://medium.com/@elizarov/callbacks-and-kotlin-flows-2b53aa2525cf outlines how they are supporting reactive streams on top of co-routines using something called Flow.
If you need a more gentle introduction to co-routines and why he picked them for Kotlin, his talk at GOTO last month is pretty interesting: https://www.reddit.com/r/Kotlin/comments/cf56gt/serverside_kotlin_with…
Thorrez · 2019-07-13
Plenty of other languages including a large percent of recent languages have the return type on the right.
Haskell, Visual Basic, Scala, F#, Go, (Rust), Kotlin, TypeScript, Swift.
Even c++ allows you to put return types on the right. Why? Because putting the types on the right allows return type deduction. I think it's better to have a single syntax (all types on the right) rather than 2 syntaxes like c++ has.
https://medium.com/@elizarov/types-are-moving-to-the-right-22c0ef31dd4…