|
|
|
|
|
by Gwypaas
1372 days ago
|
|
The issue with Go is the implicit footguns you will inevitably hit. Starting out with Go sure feels like a super power because of the simplicity and productivity, until the code base has grown and you now meticulously inspect every single line to understand the entire context a change is bringing, because you do not trust it in isolation to be correct. https://eng.uber.com/data-race-patterns-in-go/ |
|
Concurrency is tricky, and that is true in every language, but less so in Go.