>>94Non-deterministic GC overhead is
the reason languages like Go can't be used for real time systems. There are languages that try to ensure that the GC's share of a program's total execution time is well bounded (e.g., Real Time Java) but as far as I know no one has tried to do this with Go. Go's creator and major promoter (Google) does not use Go in applications where this sort of thing is a concern.
I'll agree that some of
>>1's comments on unsafe operations are off base. If you don't have a lot of code that does direct hardware interaction you can just write that stuff in C and hide it behind Go's C FFI. And if you
do have a lot of code that bangs directly on the hardware, your program is probably poorly designed. Even things like C language kernel mode drivers typically don't touch the hardware in more than a handful of carefully selected locations in the source. Anything else is hell to debug and test.