> C++18 (Out of curiosity, is this C++17 or C++20? I'd assume 17, and also I'm curious which aspects you find confusing.) Several coworkers have remarked that

> C++18 (Out of curiosity, is this C++17 or C++20? I'd assume 17, and also I'm curious which aspects you find confusing.) Several coworkers have remarked that it's just easier to reason about correctness of concurrent code in Go vs. C++, while not sacrificing performance as in, say, Python. (There's definitely a performance hit, per the use of a garbage collector.) One thing that's always bothered me about Go is just the things that are missing from the standard library; I think that contributes significantly to it being "harder" to work with. (A good number of these likely stem from the lack of generics, e.g. max(a, b int) int -- math.Max takes and returns floats.) That said, the biggest thing I liked about Go from the first day I used it was the treatment of concurrency as a first-class citizen (goroutines, channels).