Could you please stop posting unsubstantive and/or flamebait comments to HN? You've been doing it a lot, unfortunately, and we ban that sort of account. It's not what this site is for, and it destroys what it is for.

https://news.ycombinator.com/newsguidelines.html

In contrast to building fast root escalation exploits which perform useful functionality on the side, which is what we get with less safe memory models.

They are both so much more pleasant to work with than C.

Golang was created from the same people of C, it's what C++ should have been. It takes lots of background from plan9, the 'Unix++' OS.

> it's what C++ should have been

No. There's a large class of programs that you can't write in Go that you can write in C++.

No. I meant that C++ should have never been born. For high perf software C should be enough, while Go could work great for generic system binaries.

Today's low end machines are not a Pentium 2 or 3, but a Raspberry Pi B+ with 512 MB of RAM (very low end, a real life machine would be a Pentium 4 with SSE2 and 1GB of RAM or a Core Duo with 2). Enough for Go and statically linked binaries a la plan9/9front.

> No. I meant that C++ should have never been born

C++ was an important stepping stone.

There's still a large class of software for which GC-ed languages are non-starters.

I said that for that C would be more than adequate. And, yet, Go's GC can be tuned. Not for an AAA game, ok. As for C, C + SDL2 would be a good backend for any PC gaming engine.

And if we had Go instead of C++ since mid 90's, today's Go compiler would be much more performant, for sure.