4 ms·

I'm strongly convinced that the google brand name gave it a big push. Its predecessor (Limbo if I recall correctly) went nowhere. It did bring uncolored async t

I'm strongly convinced that the google brand name gave it a big push. Its predecessor (Limbo if I recall correctly) went nowhere. It did bring uncolored async to the mainstream, but as in typical golang fashion, it was very verbose and error prone. Java learned the right lessons and I'm quite excited to see their structured concurrency approach. No need to pass channels and contexts everywhere to manually manage hierarchies from what I gather.

stephen123 3y ago
Yea, I find go's concurrency very error prone compared to something with futures. I've even got a library for using futures in Go. https://stephenn.com/2022/05/simplifying-go-concurrency-with-future/ https://stephenn.com/2022/05/simplifying-go-concurrency-with...
throwawaymaths 3y ago
> It did bring uncolored async to the mainstream I believe that uncolored async (Erlang) precedes colored async (python) Correction: c# was the first language with colored aaync, still way after Erlang