Kotlin coroutines
Shares rank 6 of 11 concurrency libraries by recommenders
People recommend Kotlin coroutines as a lightweight, easy way to write async code, with structured concurrency and cancellation. Child cancellation propagating to the parent is the common caveat.
People recommend Kotlin coroutines as a lightweight, easy way to write async code, with structured concurrency and cancellation. Child cancellation propagating to the parent is the common caveat.
11 people gave an opinion
- recommend it
- 7
- criticize it
- 4
- approval share
- 64%
Recommended in 4 of 13 months
- November 2025: not recommended
- December 2025: not recommended
- January 2026: not recommended
- February 2026: not recommended
- March 2026: recommended
- April 2026: recommended
- May 2026: not recommended
- June 2026: not recommended
- July 2026: recommended
- August 2026: not recommended
- September 2026: recommended
- October 2026: not recommended
- November 2026: not recommended (month in progress)
Why it doesn’t carry the badge
- 7 people recommend itNeeds 10 or more, not met.
- 1.7 recommenders for every criticNeeds 2 to 1 or better, not met.
- Recommended in 4 of 13 monthsNeeds 4 or more, met.
The same three rules apply to every product, and the badge can’t be bought. How the badge works
What people say about it
The reasons people give, with the number of comments that give each one. Open a reason to read what they said.
Why people recommend it
Each mark is one comment
Easy, lightweight async code
“Lightweight, pauseable, resumable, cancelable and easy to use without having to provide a CancellationToken”
Comment from 9 Apr 2026 in “You can't cancel a JavaScript promise (except sometimes you can)” “If you need async, Kotlin co-routines is the easier path to do that.”
Comment from 30 Mar 2026 in “Spring Boot Done Right: Lessons from a 400-Module Codebase” Structured concurrency and cancellation
“they added structured concurrency, which roughly solves the same problem as Go's context, arguably more elegantly”
Comment from 27 Sep 2026 in “Go Concurrency Distilled” “Lightweight, pauseable, resumable, cancelable and easy to use without having to provide a CancellationToken”
Comment from 9 Apr 2026 in “You can't cancel a JavaScript promise (except sometimes you can)” Seen as better than Go
“they added structured concurrency, which roughly solves the same problem as Go's context, arguably more elegantly”
Comment from 27 Sep 2026 in “Go Concurrency Distilled” “IMO, Kotlin coroutines are better of Go's goroutines”
Comment from 18 Mar 2026 in “Java 26 is here, and with it a solid foundation for the future”
Other concurrency libraries people recommend
The four most recommended other concurrency libraries, with the same counts for each, so you can compare like for like. The tick on each bar marks the 2 to 1 line the badge needs.
| Product | Recommend | Criticize | Approval | Months | Owned | Badge |
|---|---|---|---|---|---|---|
| Tokio | 57 | 45 | 56% | 12 | — | — |
| Akka | 12 | 9 | 57% | 7 | — | — |
| ZIO | 11 | 2 | 85% | 9 | — | Approved |
| Trio Python library | 10 | 0 | 100% | 8 | — | Approved |
| Kotlin coroutinesThis page | 7 | 4 | 64% | 4 | — | — |
What people said
All 11 comments that mention it, newest first. Each links to the original comment.
“Kotlins coroutines are super super super underrated imo. I loved working with them so much before ai.”
“they added structured concurrency, which roughly solves the same problem as Go's context, arguably more elegantly”
“I just want to keep it simple.”
“the other platforms don't seem to have kotlinx.coroutines available.”
“Lightweight, pauseable, resumable, cancelable and easy to use without having to provide a CancellationToken”
“If you need async, Kotlin co-routines is the easier path to do that.”
“If you look at the bytecode it produces, it honestly is a mess.”
“IMO, Kotlin coroutines are better of Go's goroutines”
“Stupidly, child cancellation cancels the parent scope as well, unless the scope opts out by including SupervisorJob.”
“apart from kotlin-coroutines”
“kotlin's aren't serializable and the issue is inactive”
Counts come from 1,795,640 Hacker News comments, November 2025 to November 2026. How we count. Report a mistake.