Even in Go, concurrency is still not easy
Hmm, I don&#x27;t know.  I had this limited concurrency issue on the first Go program I ever wrote, and I&#x27;m very new to concurrent stuff, certainly if you only count the past ten years or so.<p>I figured this out in Go about 30 minutes after I realized I needed to limit concurrency, and I&#x27;m a dumbass, basically.<p>So, I&#x27;m not sure that &quot;still not easy&quot; is accurate, especially given that I have a lot of trouble conceptualizing async and await, as used in C#.  In fact, I don&#x27;t think I&#x27;ve ever successfully used that paradigm in C#.  I&#x27;ve been told that C# async and await are &quot;easy&quot; and this article says Go concurrency is &quot;still not easy&quot; and I&#x27;ve had the exact opposite experience in both cases.<p>In fact I really don&#x27;t understand why async and await is even a thing anymore, given the paradigm that Go uses and the example it sets.  It is almost supernatural in its ease, for me.