<p>Recently I decided to use Go for a pet project which I have prototyped in C++. My decision was based on many factors. As I was doing the re-write, I find myself questioning the language decision at many levels. The two areas which I didn't expect were compilation speed and executable size - it takes time to compile, and the executable is not of a size to brag about. It might be faster, but the advertised 3X (or any X for that matter) compilation times certainly looks like total BS at least for this project.</p>
<p>I can't avoid making the parallel to Chrome - it used to be fast and furious, until all features arrived. Now it's THE memory hog. I am wondering, is this something specific to my project, or others have noticed the same?</p>
<hr/>**评论：**<br/><br/>shovelpost: <pre><p>Are you using any non Go code in your project? Maybe C/C++ code with cgo?</p></pre>dlsniper: <pre><p>Use go install not go build. Also why do you care about the binary size? Is it in the realm of hundred of megabytes? Before jumping to conclusions have you read the manual or asked a Gopher? </p></pre>
