Why We Switched from Python to Go
Nick Parsons

I can only partially confirm your findings. I started using Python for multi-platform command line applications, but at a certain point I faced the mess of having to maintain code for multiple Python versions, and the mess of forcing the users to keep installed multiple Python versions, which was too much.

My tools are not CPU intensive, so going for a compiled language was not mandatory. I evaluated several solutions (C++, Go, Python, Ruby, Java, JavaScript), and, for my needs, the top contenders were… Go and node.js.

Go is an interesting solution, and might be the fastest, but distributing multi-platform applications seemed tedious, so the winner was node.js, mainly for its ecosystem, immediate portability and ease of use.

A small note however: I’m talking strictly about using ECMA Script 6, with async/await, since the original node.js callback style was out of question.

Like what you read? Give Liviu Ionescu a round of applause.

From a quick cheer to a standing ovation, clap to show how much you enjoyed this story.