"Quant found London girls seeking newness only too willing to try her new daring short mini skirt. The fashion trend took off because it was so different and t

"Quant found London girls seeking newness only too willing to try her new daring short mini skirt. The fashion trend took off because it was so different and to wear it well you had to be youthful to get away with an outfit that was so controversial, particularly among adults. The Quant style was soon known as the Chelsea Look." Use Go for small to medium server side systems. A lot of the issues mentioned by OP are related to scaling (in terms of codebase) stresses that Go is ill equipped to address. In the small scale, Go works like a charm. Use Go for large server side systems that compose via IPC (of whatever flavor). Lots of processes mean lots of small scale Go applications (so see above). Strongly consider Go for server side systems where 'Green Thread/Fiber/lighweight threading' is an architectural requirements. Also consider Erlang/Elixir and possibly Node. If IPC composition is also a match (see above) then Go is a serious consideration. You want a compiler in loop writing (relatively) portable cmdline tools. Go is a serious candidate here as well. I suspect a subset of the Go angst is due to philosophizing about a language that proudly wears an anti-intellectual badge on its cute furry coat. Stop doing that, accept it for what it is, and sure enough it is very useful and capable in its own niche.