<story><title>From Node.js to Go</title><url>http://blog.scaledrone.com/posts/nodejs-to-go</url></story><parent_chain></parent_chain><comment><author>Gonzih</author><text>This blog post feels very empty. No code snippets? No actuall before after benchmarks&amp;#x2F;graphs? How can you state anything without showing numbers?</text></comment>
<story><title>From Node.js to Go</title><url>http://blog.scaledrone.com/posts/nodejs-to-go</url></story><parent_chain></parent_chain><comment><author>fighting</author><text>Go seems to be still a bit of a black box in terms of performance&amp;#x2F;memory profiling.&lt;p&gt;On one recent project, the go memory profiler was showing about 35MB allocated while top showed memory usage at 500MB to 1GB. In another instance the performance profiler would show microseconds elapsed while the user experienced tens of minutes with no response from the program.&lt;p&gt;I really think they should consider including a function level profiler instead of just a sampler, as well as provide more insight&amp;#x2F;control over all the goroutines that are generated.&lt;p&gt;Just saying golang is better than node.js may not be saying all that much.</text></comment>