Hacker News Reader

Agree! It makes you wonder why they didnt try python 3.5 with async stuff, as most of their stack is based on python. Yes its not multi threaded but if the service was rewritten it might have actually performed better. Otoh: sometimes you need a good excuse to test some other technologies.

View on HN

Doesn't really make me wonder. I haven't really seen anything about python's new async stuff that indicates it's on par with node's (reply here if you found anything, I've been looking for this information!). And if python is caught up with node, it would be at very high risk of performing the same and having another random performance gotcha. Golang is one of the natural choices to replace a nodejs application for performance reasons. It's low-level, faster, uses less memory.

Care to explain why python async would have performed better? I don't see a single way in which python async would be a better alternative for the given job. I'm a python guy myself but, when it comes to async stuff, I find nodejs much better and easier to understand/follow through (even with cb madness yes). For the described job, I would have went with Elixir or Go as well yes.

Reply on news.ycombinator.com