That was not the point that I am trying to make. Of course it's faster.
It's also much closer to Python or nodejs in its use-cases than C++, while still being faster. It's not meant as a replacement for other compiled languages, it is intended for backends.
Yeah Go is basically a scripting language. Most users are coming from Python, Ruby, etc. The original idea that people at Google would migrate to Go from C++ never happened. It’s used as a logs analysis tool that non-CS data scientists can write, with no fancy features at all, to prevent them from crashing batch dataflow pipelines that are running offline, seamlessly scale horizontally, and have no direct production impact if they miss deadlines. The application code for real time serving is all in C++ because Go is too slow and unpredictable at runtime, and the teams are staffed by people with strong software backgrounds. The whole “Go as a systems language” or “Go as a cloud services language” is kind of laughable. It’s like those Tik Toks that say No One: and then it’s Go fans claiming the language has a strong suit other than keeping people who haven’t passed CS 101 from crashing the batch job, productivity speed and control for concurrent real time services be damned.
Proper backends are written in compiled languages already long before Go was born, C#, Java, C++, D, Rust, F#, Ocaml, Haskell.
Anyone using scripting languages to write backends is only accumulating technological debt, increasingly writing C extensions to duck tape their lack of performance.
A lesson learned with AOLServer, Zope and mod_perl in early 2000, but it seems everyone has to face their own destiny instead of learning from others.
