Hacker News Reader

I love the anecdotal account -- especially since I am researching a similar change -- but would truly appreciate more numbers for transition stories like this. Memory usage before and after. Throughput, etc.

Also what was the cost in time and man hours of conversion?

View on HN

It really depends on how much experience someone has with Go. It will be more hours for sure than Node, probably more code also. You need to watch out on couple of things also that you don't need in Node. For example default passing by value to functions so you need to use pointers for large structs if you want performance, you need to know that strings are immutable which means that if you do something like "some" + "ting" you are basically creating new string and both strings are copied to that string, if you have a lot of that kind of operations (like really a lot) then use bytes.buffer etc. A lot of things that are not so obvious for beginner in Go. But you got great tools at your disposal by default like pprof which is great profiler, data race checker etc. Standard tooling is really great.

Strings in javascript/nodejs are also immutable.

You will appreciate this: https://medium.com/@theflapjack103/the-way-of-the-gopher-669...

Reply on news.ycombinator.com