I think the real issue is that Go is its runtime, including garbage collection but also coroutine scheduling, syscall management (syscalls effectively enter 'go

I think the real issue is that Go is its runtime, including garbage collection but also coroutine scheduling, syscall management (syscalls effectively enter 'gospace' before kernelspace), etc. Go's docs liken it to crt0, which is entirely dishonest. You can't have verifiable deterministic programs with a runtime like this which extends way beyond a small setup routine. That's generally 'fine in practice' for application development - especially the Python-level programs which are generally written in Go - but for building another language (interpreter) atop it, it strikes me as madness.