kohlrak: A little late jumping in here, but this is why i switched from C++ to C: While i loose fancy things like operator overloading, and
this, i gain alot more in knowing the code i wrote won't be broken due to deprecation of language features (it's coming, thanks to Google, and the failure of their language GO to really catch as much as they wanted). Another thing I do is homebrew what I can or pull in FOSS sources that aren't likely to need frequent updates (i think the LZMA libs are pretty well established, for example). Unfortunately, that might be a bit much for gogrepo, however.
Thing is, C++ is mostly a superset of C (or was a decade ago when I was doing a lot of C++ anyways). Python 3 is not a superset of Python 2. They didn't just add stuff on top of Python 2. They broke things with Python 2.
You have to put a lot of "if" and "catch" statements to support both versions and equally importantly, you have to validate what you are doing across both python versions (unless you have automated pipelines which themselves will require time to implement, that's a lot of manual overhead).
I remember about 6 years ago when I was working on the Insomnia Sale script with phoeniixz. I believe she was using Python 3 and I was using Python 2 at the time. We were breaking each other's stuff a lot.
Otherwise, for Golang, I don't think its the end-all solution for everything (what is?). Its too low level to get things done yesterday (Python and Javascript still shine for that), but for portable binaries and operational cloud solutions (where it carved itself as the dominant player), it really shines.
I mean, right now, I have a self-contained binary in Golang that is less than 20mb, that will run by itself cross-platform on Windows (both 32 bits and 64 bits), MacOS, and Linux. The only way I could approach that with Python/Javascript is with Docker and even some of the developers struggle with that, nevermind non-technical users.