I was going to comment on TypeScript as well... I find that it&#x27;s when modules become too big, ill-named or just hard to follow that is when things get hairy.  TypeScript (and Angular, while I&#x27;m at it) tend to favor larger class-style modules.  It&#x27;s harder with a dynamic language, and TypeScript doesn&#x27;t inherently make it better.  As for Angular, mentioned before, I really don&#x27;t like their DI system and really favor Node&#x27;s CommonJS or ES6 module references.<p>Agreed on single-threaded runtimes... you can get around them, as far as robustness goes, you bring in the same techniques used to scale to multiple servers, you&#x27;re just doing it a little sooner.<p>I haven&#x27;t done enough in Go to really comment, it looks cool, though I haven&#x27;t had a use case that I really needed more performance than what I already have with the other tools available.