/r/Haskell currently has a thread on why Haskell sucks. Why do you think Go sucks?

<p>We need some more material for our <a href="https://wiki.theory.org/YourLanguageSucks" rel="nofollow">YourLanguageSucks</a> entry.</p> <hr/>**评论：**<br/><br/>scorbuticgopher: <pre><p>The <a href="https://golang.org/doc/faq#nil_error" rel="nofollow">non-nil nil</a> thing is missing from the list. That&#39;s a legitimate complaint. Some of these other complaints, however, seem silly.</p> <blockquote> <p>The select statement is blocking, but if you add a default case it suddenly isn&#39;t.</p> </blockquote> <p>Why is this bad? How else would the default case work? This is the obvious way for it to work.</p> <blockquote> <p>Go does not require break at the end of every case in a switch statement</p> </blockquote> <p>I hate that you have to write <code>break</code> at the end of every case in C# even though there&#39;s no fallthrough. There&#39;s no need for a superfluous <code>break</code> if there&#39;s no fallthrough. What&#39;s the problem?</p> <blockquote> <p>If you import a library or declare a variable, but do not use it, your program will not compile even if everything else is valid. Debugging is fraught with adding and removing &#34;import&#34; statements.</p> </blockquote> <p>Use <code>goimports</code>. Variables can cause trouble, however. On the other hand, an unused variable is often a bug, and the Go compiler has helped me catch many bugs with this <em>feature</em>.</p> <blockquote> <p>Go&#39;s error type is simply an interface to a function returning a string.</p> </blockquote> <p>So? You can add whatever you want to your own <code>error</code> types, you can even create your own interface for errors. Again, what&#39;s the problem?</p></pre>SteveMcQwark: <pre><blockquote> <p>The <a href="https://golang.org/doc/faq#nil_error" rel="nofollow">non-nil nil</a> thing is missing from the list. That&#39;s a legitimate complaint.</p> </blockquote> <p>On the one hand, it makes perfect sense that the nil interface value is different from an interface with a typed nil value in it, especially since you can actually call methods on a nil pointer without issue. On the other hand, it could maybe have been clearer by using a different name for an interface&#39;s zero value.</p></pre>tuxlinuxien: <pre><p>I can give you materials for YourLanguageSucksSucks instead</p></pre>bmurphy1976: <pre><p>Do we really need this here? I come here to get a respite from the constant Go bashing everywhere. It&#39;s not perfect, we know that, we don&#39;t care. Time to move on.</p></pre>dgryski: <pre><p><a href="https://github.com/ksimka/go-is-not-good" rel="nofollow">https://github.com/ksimka/go-is-not-good</a></p></pre>1Gijs: <pre><p>&#39;We&#39; should grow up: stop whining and be master of our own destiny.</p> <p>So either: 1) Get over it and love Go &#39;as-is&#39; 2) Move to another language (there are so many - take your pick) 3) Create your own language or dialect (be bold)</p></pre>itsmontoya: <pre><p>Lack of generics</p></pre>shovelpost: <pre><p>Your Go list is bad and you should feed bad.</p></pre>brogrammingsins: <pre><p>This generic question makes one say: because of threads like this... </p></pre>