Linux Namespaces and Go Don't Mix
This leads to go code being roughly as messy&#x2F;clumsy as C (or whatever else) code in the sections that need concurrency and also need to change namespace. That&#x27;s unfortunate, but I don&#x27;t know that it really &quot;raises a few eyebrows&quot;.<p>I mean, what&#x27;s the better alternative to Go for this work? Maybe Rust? It is, at least more controllable at a lower level...but, not as easy to pick up for people coming from a C&#x2F;Python&#x2F;Perl&#x2F;Ruby systems and ops background. I&#x27;m not saying one <i>should</i> use Go for containers&#x2F;namespaces programming, but a lot of people are with some success (probably also banging into the namespaces issue now and then), I&#x27;m just saying it&#x27;s not obvious to me what the better alternative would be.