Thread

Go Concurrency Distilled

402 points · 187 comments · chmaynard

SamInTheShell · 1790469542 · focus · HN ↗
The concurrency and threading in Go just feels like magic compared to every other language. I'm a goroutine addict and I refuse to be rehabilitated.
Just from observations over the years, I don't think there's any other language quite like this, in terms of how things can end up happening in any thread.
1. osigurdson · 1790472477 · focus · HN ↗
  >> in terms of how things can end up happening in any thread
  Doesn't that describe pretty much any green thread style concurrency implementation.
  1. dlisboa · 1790477447 · focus · HN ↗
    No. Preemptive scheduling plus M:N mapping combination that Go has is not common in other major implementations.
    Other languages and their implementations of green threads usually have cooperative scheduling or M:1 mapping
    seabrookmx · 1790488892 · focus · HN ↗
    C# and Rust (via Tokio) both have M:N threading. They both use a work-stealing algorithm to map many tasks onto a finite thread pool. But you're correct that they are cooperative via async/await, not pre-emptive.
    smw · 1790519665 · focus · HN ↗
    I feel like you can't describe something as m:n when it the m uses async/await and doesn't actually have a green thread?
    seabrookmx · 1790522977 · focus · HN ↗
    Define the "green thread"? By every definition I've seen[1], the task objects I mention are green threads.
    [1]: <a href="https://en.wikipedia.org/wiki/Green_thread" rel="nofollow">https://en.wikipedia.org/wiki/Green_thread

Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.