> For anything else it (or any form of Javascript) isn't the right tool for the job, in part for the reasons outlined in this post. I genuinely don't understan

> For anything else it (or any form of Javascript) isn't the right tool for the job, in part for the reasons outlined in this post. I genuinely don't understand how someone could make a statement like this. You mention command line apps and servers, but surely whether TS is the best solution would depend entirely what you're trying to achieve. If there's a great NPM library to help you with the problem you're solving why wouldn't you use TypeScript? Not to mention the fact that TypeScript servers when paired with web frontends have obvious advantages. One project I worked on involved analysing 3D objects then visualising this on a web app. The simplest solution we found for visualising the analysis we were doing on the backend was just to build it all with Three.js and TypeScript then use common libraries. I'll also note that good JS developers are generally competent enough to avoid "bad habits" and that "bad habits" in my experience are not isolated to the JS ecosystem.