Go is a systems language. The term isn't confined to device drivers. It includes platform/backend software such as web servers and things like message queues or the Docker ecosystem.
The term is nebulous though.
The term is nebulous though.
By your argument Ruby and Python are also systems languages because they can be used to write servers and job queues.
You're not doing real time programming with Go. Don't make systems programming lose its meaning by promulgating this myth.
I think you're conflating writing device drivers/kernels with systems programming, which includes those things but is not limited by them.
Regardless, the term's meaning can't be lost if its apparently this hazy.
You will note that rust advertises themselves as a systems level language and it is deliberately designed with the term zero cost abstraction. All this means is predictable asm from code. No black magic. Rust is advertised as systems level and this is the property that enables it. I hope that allows you to understand what it means to be systems level.
I truly believe that you are completely wrong and only few languages nowadays are system languages without a GC. C++, C, D (when used without the GC) and rust are examples. All the other languages you listed aren't.
I follow the line of thinking that includes utility software and backend services/platforms as described here:
https://en.wikipedia.org/wiki/System_programming_language
Hence, the word has different meaning from person to person. So there is no wrong, or at least it exists on a spectrum, and everyone complaining about the original comment's word choice is just jerking their ego off.
> Real-time programming can be done in any language, Java for example
That's absolute bullshit. Please get a Computer Science education before making yourself look like a fool.
Edit: we've had to warn you about this repeatedly. Please fix this so we don't have to ban you.
This is literally impossible with a GC because you can only bound one resource (time or memory) at a time.
The best RTS languages are a pain in the ass to use because the compiler will complain about every single thing - cases that could go wrong with your code
They are used in mission critical (in all sense of the word) systems like spaceships - where a tiny bit of lag will send it thousands of miles in the wrong direction.
Those links you provided, one is a draft for a spec, it's not even implemented yet - and the other has nothing to do with real time languages.