7 ms·
I don't see how Go was ever aimed at replacing C for systems programming, heck, both the Go runtime and the Go compiler is written in C.
by gillianseed 14y ago
I don't see how Go was ever aimed at replacing C for systems programming, heck, both the Go runtime and the Go compiler is written in C.
- codygman 14y agoCouldn't you also say "I don't see how C was ever aimed at replacing assembly for systems programming, heck the C runtime and compiler is written in assembly." Feel free to correct me if I'm wrong.
- gillianseed 14y agoOk, the c runtime and compiler is not written in assembly.
- 1SaltwaterC 14y agoThis argument is getting old. What was the first, the egg or the chicken? Was the first C implementation passed down on stones drawn from the void of the Universe? At some point bootstrapping was needed for the implementation to be self hosted. That goes for every supported platform.
- gillianseed 14y agoOf course not, but once they existed C compilers has been written in C (or later C++), not assembly. Go exists, the runtime and the compiler is written in C and from what I've read from Russ Cox there are no plans whatsoever of rewriting either in Go.
- 1SaltwaterC 14y agoOf course. But for the moment, being self hosted is just reinventing the wheel when there's so much existing infrastructure. That being said, it is difficult, probably impossible, for Go to be a C replacement, but you're using the wrong argument (the current canonical implementation).