<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>37ef_ced3</author><text>Anyone who works on large C++ projects will laugh at your &amp;quot;several minutes&amp;quot; comment. You may not realize how bad things are on the other side of the fence</text><parent_chain><item><author>jsjsbdkj</author><text>Go is mostly very good, but the module ecosystem continues to be a nightmare, and having a deep dependency graph can make build times brutal. I work on a project which depends on k8s, which means a cold build take several minutes. Not to mention trying to update dependencies and figure out what versions are actually being built into the final binary.</text></item><item><author>37ef_ced3</author><text>As a developer I continue to be extremely happy with the Go language and the Go tools. Over the past 5 years Go has almost entirely replaced my use of C and C++. My Go programs (e.g., &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;NN-512.com&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;NN-512.com&lt;/a&gt;) are reliable, run fast, build fast, require no shared libraries, and have airtight error handling. Unfortunately, C++ is still necessary for my commercial work and I am amused daily by the absurd complexity and clumsiness of expression, slow builds, dynamic linkage problems across Linux releases, etc.</text></item></parent_chain></comment><story><title>Go 1.17 Beta</title><url>https://tip.golang.org/doc/go1.17</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>morelisp</author><text>K8s is a massive outlier in Go build times. Several minutes for cold build times is a blessing. Lots of C++ builds still run overnight. Composer takes 3 minutes just to validate the dependency graph in one of our older PHP projects.</text><parent_chain><item><author>jsjsbdkj</author><text>Go is mostly very good, but the module ecosystem continues to be a nightmare, and having a deep dependency graph can make build times brutal. I work on a project which depends on k8s, which means a cold build take several minutes. Not to mention trying to update dependencies and figure out what versions are actually being built into the final binary.</text></item><item><author>37ef_ced3</author><text>As a developer I continue to be extremely happy with the Go language and the Go tools. Over the past 5 years Go has almost entirely replaced my use of C and C++. My Go programs (e.g., &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;NN-512.com&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;NN-512.com&lt;/a&gt;) are reliable, run fast, build fast, require no shared libraries, and have airtight error handling. Unfortunately, C++ is still necessary for my commercial work and I am amused daily by the absurd complexity and clumsiness of expression, slow builds, dynamic linkage problems across Linux releases, etc.</text></item></parent_chain></comment><story><title>Go 1.17 Beta</title><url>https://tip.golang.org/doc/go1.17</url></story>