Go channels are bad
I think I&#x27;ve just come to accept that sychronization is the pain point in any language. It&#x27;s callbacks, promises, and the single event loop in nodejs. It&#x27;s channels in golang.<p>No one can come up with a single abstraction for synchronization without it failing in some regard. I code in go quite a bit and I just try to avoid synchronization like the plague. Are there gripes I have with the language? Sure, CS theory states that a thread safe hash table can perform just about as well as a none-thread safe, so why don&#x27;t we have one in go? However...<p>Coming up with a valid case where a language&#x27;s synchronization primitive fails and then flaming it as an anti-pattern (for the clicks and the attention, I presume) is trolling and stupid.