[ivan4th]

I was looking forward to the fix for the dreaded Linux namespace handling problem: https://www.weave.works/blog/linux-namespaces-and-go-don-t-m... which kind of makes Go suck for many important container-related tasks. But apparently the effort has stalled... https://go-review.googlesource.com/c/go/+/46033

[bradfitz]

It doesn't look stalled. It looks targeted towards Go 1.10, not Go 1.9.

[valarauca1]

There really aren't great solutions to this in C/C++ having one application share state/memory across namespaces/users is a v hard problem

[dullgiulio]

This has been discussed and the discussion derailed very quickly ("Go is a joke, my language has it bigger, blah blah".)

Reality is that the Linux Kernel makes a big confusion between processes and threads in the userspace APIs.

Locking to threads is a solution that works but also sucks and defeats the niceties of Go N:M model. But that's the only way: if you use that broken system calls API you should know better.