<story><title>The simplicity of single-file Golang deployments</title><url>https://www.amazingcto.com/simplicity-of-golang-systemd-deployments/</url></story><parent_chain><item><author>drewg123</author><text>The fact that it produces a single static binary is one of the nicest things about golang.&lt;p&gt;This used to be easy with C (on BSD &amp;amp; Linux) a long time ago, but then everything started to depend on various shared libs, who then depend on other libs, then things started to even dlopen libs behind your back so they didn&amp;#x27;t even show up in ldd, etc.  Sigh.</text></item></parent_chain><comment><author>quaintdev</author><text>&amp;gt; The fact that it produces a single static binary is one of the nicest things about golang.&lt;p&gt;Not only that it can also cross compile for different architecture and operating systems.</text></comment>
<story><title>The simplicity of single-file Golang deployments</title><url>https://www.amazingcto.com/simplicity-of-golang-systemd-deployments/</url></story><parent_chain><item><author>drewg123</author><text>The fact that it produces a single static binary is one of the nicest things about golang.&lt;p&gt;This used to be easy with C (on BSD &amp;amp; Linux) a long time ago, but then everything started to depend on various shared libs, who then depend on other libs, then things started to even dlopen libs behind your back so they didn&amp;#x27;t even show up in ldd, etc.  Sigh.</text></item></parent_chain><comment><author>candiddevmike</author><text>From what I have seen in major OSS projects like systemd and PostgreSQL, nothing seems to support static linking, to the point where some contributors get annoyed when you ask for it.&lt;p&gt;Seems like the C&amp;#x2F;C++ ecosystem will stay dynamically linked, even with a lot of the industry shifting towards statically linked, fat binaries as disk space is pretty cheap.&lt;p&gt;I wonder how much simpler Linux packaging would be if everything was statically linked...</text></comment>