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. tym0 · 1790515634 · focus · HN ↗
  We're heavy user of Go at work. Go also makes it way to easy to write bad concurrent code and hard to write good one.
  Stick to err/wait group and go routines and it's OK. Any PR with a channel or mutex I'll assume the author made a mistake.
  1. lolpython · 1790515975 · focus · HN ↗
    Asking as an outsider to Go. How do you communicate between threads without a channel or mutex?
    osigurdson · 1790517159 · focus · HN ↗
    A goroutins shares memory so you can just share variables if you want. It is basically the same as any other language in this regard.
    treyd · 1790517457 · focus · HN ↗
    It's also just as easy to incorrectly share memory and cause race conditions. There's no protection against it and it violates memory safety.
    osigurdson · 1790538575 · focus · HN ↗
    For sure. The parent comment was merely asking if it could be done without channels or mutex, not if it was a good idea or not. Of course sometimes it is indeed the right thing to do.
    osigurdson · 1790552345 · focus · HN ↗
    Haha! Laughing at my own comment: "a goroutins shares memory". The iPhone keyboard wins again.
    tym0 · 1790548300 · focus · HN ↗
    Wait groups do use concurency primitives underneath. My point is that the primitives that go provides are too easy to use incorrectly. And the language makes it hard to build nice abstraction on top of them. So I generally steer people away from using them unless strictly necessary, channels in particular.

Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.