[justincormack]

tcp was designed a long time ago when computers were slow, and precise timing is not a hard requirement; also you can design a stack so it doesn't allocate in the fast path (gc or not, allocation is slow). That said, Go is still a weird choice as the runtime is not ideal for system applications.

[pjmlp]

Not really, here are some examples of systems done with GC enabled systems programming languages.

https://github.com/ycoroneos/G.E.R.T

https://archive.org/details/bitsavers_xeroxparcteCedarProgra...

http://www.hpl.hp.com/techreports/Compaq-DEC/SRC-RR-6.pdf

http://www.projectoberon.com/

http://www.ocp.inf.ethz.ch/wiki/Documentation/Kernel

https://en.wikipedia.org/wiki/ARX_(operating_system)

https://en.wikipedia.org/wiki/SPIN_(operating_system)

https://www.amazon.com/Programming-Modula-3-Prentice-Innovat...

[justincormack]

I specifically said gc was not an issue but that Go's weird threaded runtime was more of an problem. You missed Mirage from your list, among others.

[pjmlp]

I specifically stated some examples. The purpose wasn't to list them all.

Mirage OS has the problem that it still relies on Xen, so sometimes listing it gives argumentation power to those disregarding the dependency as a convenience, rather than lack of support on OCaml for such kind of programming.

Go's weird threaded runtime is nothing new. That is how Active Oberon tasks (aka Active Objects) are implemented.