News for hackers. Stuff that matters.
Re:Gopher Wrangling. Effective error handling in Go by za3faran on Tuesday June 20, 2023 @01:53AM (#36400235)
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.

Re:Gopher Wrangling. Effective error handling in Go by throwawaymaths on Tuesday June 20, 2023 @03:23AM (#36400762)
> 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

Re:Gopher Wrangling. Effective error handling in Go by stephen123 on Tuesday June 20, 2023 @03:26AM (#36400778)
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...