Golang Concurrency Design Considered Harmful (opens in new tab)

(medium.com)

34 pointscopyconstruct8y ago4 comments

4 comments

'Considered Harmful' Headlines Considered Harmful

I love how everyone can write a 'Considered Harmful' headline by figuring out something along the line of "I don't like it, therefore it must be bad, therefore I consider it harmful".

It's time to stop. This stopped being funny months ago.

zzzcpan8y ago

There is a difference between having serious flaws and not liking it. Go's idiomatic concurrency is in the first camp and should be considered harmful.

Toine8y ago

Years ago

exacube8y ago

1) using channels + goroutine to implement a map doesn't seem like the most sensible thing to do; even golang's new sync.Map type is implemented with mutexs (eg https://github.com/golang/sync/blob/master/syncmap/map.go#L2...). Idiomatic doesn't mean ALWAYS do this no matter what; it is the natural thing to do if it feels like the right approach.
2) Don't use "considered harmful" so much; it is considered harmful.

j / k navigate · click thread line to collapse

4 comments

phoe-krk8y ago

'Considered Harmful' Headlines Considered Harmful
I love how everyone can write a 'Considered Harmful' headline by figuring out something along the line of "I don't like it, therefore it must be bad, therefore I consider it harmful".
It's time to stop. This stopped being funny months ago.

zzzcpan8y ago
There is a difference between having serious flaws and not liking it. Go's idiomatic concurrency is in the first camp and should be considered harmful.

Toine8y ago
Years ago

exacube8y ago

j / k navigate · click thread line to collapse