Why ever use Go over modern C++?

because you want to finish a project in a day rather than a month

Because C++ is an unholy monstrosity that extremely few people fully understand.

>>61805080
/thread

>>61805080
Isn't keeping incompetent programmers out of the field a good thing, though?

>>61805031
just try getting multithreading right in both and you'll know the answer

Go has nice networking (all network stuff is done using epoll/kqueue/etc under the hood) and great concurrency features, but I wouldn't use it for anything other than networking applications.

>>61805121
You'd think that, but C++ is the world's second most prolific generator of incompetent programmers.

>>61805269
HTML is the first.

>>61805301
I was going for Java. Not being a programming language, HTML is only capable of generating incompetent markup writers.

>modern C++
is a meme

Not only it is constantly moving target but the word itself doesn't tell you anything about the codebase other than it has a compiler which supports c++11 or higher. There must be thousands of different ways of writing modern c++ and the number can only increase.
Every project uses different permutation of practices and features. The core guidelines project is pathetic attempt to normalize everyone to using the same set of practices. Too bad it's lead by academic types who don't understand why there are so many different ways to use c++ in the first place. Good thing is everyone can ignore it.

Go is relatively easy to write allows for ok performance and works for things that don't have soft or hard real-time requirements.
If you really must care about performance, then just use C instead of C++