<hr/>**评论：**<br/><br/>BurpsWangy: <pre><p>So your solution to what you found would be ANOTHER language that transpires into Go?</p>
<p>Just go find another language and leave Go alone, if you don't find it fitting your needs. I dunno WTF is with all these people coming out of the woods attacking Go all of a sudden. I've been using it over 3 years now and not once ran into problems with which I had issues. .NET... I did... constantly. Go has been the most lightweight, solid performing, and fun language I think I've ever used. For this... I'll stick with it.</p>
<p>I feel bad for newcomers coming to the language. All I see now is hate, people bitching about generics, and why it's not more like {insert other language}. I also see a LOT of blogs and articles giving bad code and advice. Not sure WTF that's from. All of a sudden, everybody is a fucking know-it-all, and suddenly knows why Go isn't and what Go should be... but they continue to get things wrong. It's embarrassing for the Go community.</p>
<p>Go has one of the best communities, awesome standard library, with some of the smartest folks in CompSci behind it. Period.</p></pre>internetperson104: <pre><p>this.</p></pre>Bstochastic: <pre><p>FWIW I'm a newcomer and I'm loving go. Taking the advice of the community and reading more before I complain.</p></pre>mrkaspa: <pre><p>I agree that Go has a great community, you are not one of them though, I've used Go since 4 years ago, there are good things on it, but somethings need improvement that's why they decided to build Golang 2 listening to the community which is a great decision. I think Golang as a transpiling target could be great because of the tooling and the libraries, and I've seen some attemps to build something such as oden, goby or have.</p></pre>arp242: <pre><p>Quirks? Huh? Go is one of the quirkest-free languages that I know.</p></pre>mrkaspa: <pre><p>There are a lot <a href="http://devs.cloudimmunity.com/gotchas-and-common-mistakes-in-go-golang/" rel="nofollow">http://devs.cloudimmunity.com/gotchas-and-common-mistakes-in-go-golang/</a></p></pre>arp242: <pre><p>A lot of those aren't "quirks"; you can do lists like this for every language.</p>
<p>The intro to that article says exactly that:</p>
<blockquote>
<p>Go is a simple and fun language, but, like any other language, it has a few gotchas... Many of those gotchas are not entirely Go's fault. Some of these mistakes are natural traps if you are coming from another language. Others are due to faulty assumptions and missing details.</p>
<p>A lot of these gotchas may seem obvious if you took the time to learn the language reading the official spec, wiki, mailing list discussions, many great posts and presentations by Rob Pike, and the source code. Not everybody starts the same way though and that's OK. If you are new to Go the information here will save you hours debugging your code.</p>
</blockquote></pre>recurrency: <pre><p>Lol</p></pre>Haetze: <pre><p>That may depend on what you see as a quirk, but maybe <a href="http://havelang.org/" rel="nofollow">http://havelang.org/</a>. It's not stable and I haven't used it though.</p></pre>mrkaspa: <pre><p>havelang is abandoned</p></pre>natefinch: <pre><p>Likely a common property of transpilers to go. </p></pre>weberc2: <pre><p>((popcorn))</p></pre>
