Go is not a wannabe C++ replacement.
It could be, but its designers aren't keen in modern language design.
First it needs to fulfill more use cases than Docker and Kubernetes ecosystem.
And while TinyGO and TamaGo exist, they require custom runtimes, and Assembly tricks that C++ supports at the language level, or even Rust does better than Go.
It is better than using Oberon-07 minimalist design, though.
I agree 100%. Just pointing out there’s efforts in this area for better or worse.
My rant is really about sensible defaults that should enforce security and standards (stdlib after all) instead of having to juggle archaic edge cases from hardware of 30 years ago or adding more keyword sugar to your signature to make it through.
Go is fun to write though.
Can you expand on Oberon-07 minimalism in the context of bootstrapping or working at the lowest level of abstractions?
Your posts about the Wirth tradition languages and their implementations are typically well founded and I haven’t read much on this aspect. If you just have a reference you’d suggest that would be more than enough (if you don’t want to take time explaining what has been written elsewhere).