Yeah but that means if you want to fix things at the libc level, you necessarily skip Go. OpenBSD had/has this problem.
But more broadly, I think the policy is less "Unix took a wrong turn" and more that goroutines make C/Go interop painful.
But more broadly, I think the policy is less "Unix took a wrong turn" and more that goroutines make C/Go interop painful.
Go 1.0 is basically Limbo with a bit of Oberon-2 syntax.
Outside the chocolate factory, it would have been just as successful, to the point that everyone forgets about Inferno and only talks about Plan 9.