Conc: Better Structured Concurrency for Go

Re:Conc: Better Structured Concurrency for Go by Smurfix on Thursday January 12, 2023 @08:16AM (#34353003)

Well, Ok, so the main thing that's good about it is that it's dead easy to start a goroutine. But that's actually bad, just like randomly jumping to any piece of code whatsoever is bad in in a procedural language.

Read the Structured Concurrency notes (https://vorpus.org/blog/notes-on-structured-concurrency-or-g...) for the reasons why.

[ Parent | on HN ]

Re:Conc: Better Structured Concurrency for Go by philosopher1234 on Thursday January 12, 2023 @08:51AM (#34353442)

I don’t know. I think the culture around go encourages effective/safe strategies for using go routines + channels. I think when channels are used as intended they can be quite effective. They’re not technically more safe than anything else, but I think the fact that they make concurrency more manageable is good.

[ Parent | on HN ]