Great, relevant reply, Nick — thanks for taking the time to share your thoughts & experience.

I think it’s important to stress that the first reason why we built our app with .NET was our founder’s fluency and efficiency with it. At the time (2013), both tech & business constraints put us in a position where we needed to build something solid, quick. Also, I’d argue that the JS ecosystem wasn’t as developed and solid as it is now.

As for today, I’d say the gains (more modern, sexier tech stack) we’d have from a complete switch to JS/Node wouldn’t justify the costs incurred (time, resources, team-wide skills to develop, refactoring, money, etc.). And to be honest, should I have total liberty picking a stack for a complete rewrite, I’m not convinced I’d lean towards Node (or .NET for that matter) — other stuff like Clojure and Elixir have been quite interesting to me lately.

But maybe we were too eager to prone .NET for *others* in our concluding thoughts… I don’t know. I think I still stand by the concluding line of “use tech that enable you to get sh*t done quickly.”