<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>hellcow</author><text>I&amp;#x27;ve been using go modules in my company for several months now. Everything has &amp;quot;just worked.&amp;quot; It&amp;#x27;s at least 1 order of magnitude faster than dep.&lt;p&gt;It&amp;#x27;s worth noting that go modules use a novel dependency resolution algorithm which is extremely simple to reason about&amp;#x2F;implement, fast, and produces more reliable builds than npm&amp;#x2F;bundler&amp;#x2F;cargo. That&amp;#x27;s why I was excited about it, anyway. It removes the ever-present NP-complete assumptions in this space, so from a computer science perspective it&amp;#x27;s extremely interesting.</text><parent_chain></parent_chain></comment><story><title>Taking Go modules for a spin</title><url>https://dave.cheney.net/2018/07/14/taking-go-modules-for-a-spin</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>ainar-g</author><text>I am eagerly awaiting the arrival of the module system, but please note, that it&amp;#x27;s still experimental, so not all fun and rainbows. As of now, the Go issue tracker still has 53 open issues with the &amp;quot;modules&amp;quot; label[1], and Go 1.11 should ship around August. The system works well for most cases, but there are still rough edges, especially around vendoring, undocumented or not-so-well documented behaviours, and features which may or may not be &amp;quot;in the scope&amp;quot; for the module system.&lt;p&gt;Overall, I am trying to be optimistic about the future of Go dependency management, but I am not planning to switch the projects I work on in my company from dep to Go modules until most of those rough edges are either smoothed, or officially recognised as &amp;quot;works as intended&amp;quot;, with viable workarounds.&lt;p&gt;[1] &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;golang&amp;#x2F;go&amp;#x2F;issues?q=is%3Aissue+is%3Aopen+label%3Amodules&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;golang&amp;#x2F;go&amp;#x2F;issues?q=is%3Aissue+is%3Aopen+l...&lt;/a&gt;</text><parent_chain></parent_chain></comment><story><title>Taking Go modules for a spin</title><url>https://dave.cheney.net/2018/07/14/taking-go-modules-for-a-spin</url></story>