Re:The ecosystem of the Go programming language
by cratermoon on Monday March 22, 2021 @01:02PM
(#26543504)
Go was built as a language to make communicating sequential processes[1] first-class citizens. Thus the ubiquity of channels and goroutines. No locks, no condition variables, no callbacks[2]. Writing a bunch of code using locks and callbacks in Go goes against the grain of the language.
1. Only superficially, because they all share the same basic flow-control constructs and (except for Python) the same C-inspired syntax. They all have totally different standard libraries, package ecosystems, etc.
2. I don't see what makes Go exempt, other than "wow great they didn't add generics bless the Go core team."