[anthk]

Rust and C++'s overcomplex syntax are a nightmare to maintain and set.

Go should have been the C succesor long ago, at least for 64 bit machines. In the end It's from the same people of Unix/C/Plan9, so they know their flaws and reasons.

For C++ like performance, sadly there's nothing close to Rust, but Zig and Nim can be close and good enough. Inb4 "mah objects", just use Java or C# and forget C++ forever for OOP programming. The sooner, the better. If you like using C++ just as an improved C and hate templates and objects, just use it for QT5/6 and some performing games and applications. Go can handle the rest just fine.

What I'd love is to see projects like Cataclysm DDA:Bright Nights rewritten in Go, they could save tons of issues on compiling (Clang 11 here, a nightmware to compile) and running, because for an open world game using the GC would free tons of waste on references and objects ingame. Also it will compile much faster and it could be ported to most platforms with no efforts at all.

And I say this as an ScummVM user and sometimes I like debugging some old adventure and RPG games under it...

[bergkvist]

Golang is not a replacement for C. It is a much higher level language, which doesn't play well with systems programming/embedded development etc.

[anthk]

Tell that to the C creators.

[egorfine]

Problem with C++ is that it allows an overcomplicated code.

[yencabulator]

Go doesn't help with memory safety in concurrent settings, and a kernel is very much that.