The GopherJS project first caught my attention about 2 years ago, back when few parts of the Go spec were implemented. However, I noticed the incredible pace at which Richard was working, making multiple sophisticated commits per day, as well as fixing reported compiler…
Great article, thanks.
I’d move #9 on top as many developers neglect this fact and focus on other parts of their design in terms of performance. In other words, your program is as fast as the slowest part, which is usually I/O.
I’d add this the the bullet point #5: don’t sacrifice readability for performance.