CTO at Style Arcade·
Chose
Node.jsNode.js
over
JavaJavaGoGo

Node.js has been growing in popularity, and the ability to access the global pool of Javascript developers is great. There is a decreased amount of effort for people to work across the frontend and backend, and the language itself is easy and works well for many common use cases.

Go was the other serious candidate, but it just hasn't been implemented in as many Production systems yet, and the best Go engineers I've known have been hackers, whereas we're building a robust analytics platform that requires more caution. Type safety is easily added with TypeScript, and NPM is awesomely handy.

READ LESS
10 upvotes·1 comment·146.8K views
Simon Aronsson
Simon Aronsson
·
March 10th 2020 at 2:17PM

For what it's worth, we're using go at k6 as the backbone of our tool. From what I can tell, we've yet to regret that decision. Would be awesome to hear your thoughts in a year or so, when you might have noticed the potential tradeoffs in terms of performance. 👍🏻

·
Reply
Avatar of Brent Maxwell

Brent Maxwell

CTO at Style Arcade