Any project / tool should be written in the language most suited for the problem, while also pragmatically factoring in prior experience of those who would do s

Any project / tool should be written in the language most suited for the problem, while also pragmatically factoring in prior experience of those who would do said work. Is there really a significant overlap between programming tooling usage, and development of the programming tools? The case where I see most rampant abuse of this is npm/node commandline tools. Written in/for an environment because it is mostly used by people in that environment, and not because it is particularly suited for it. If it wasn't for docker, all those tools would be tied to a exceptionally messy runtime, and wasted effort. They also won't be included in any normal distribution either. It makes any tool written in node to come across as an amateurish and hacked together attempt. Regardless of how well and robust it is. I'm sure there are good reasons for it, beyond my understanding, since node is something I've always avoided due to red flags all around. But, I digress. If the memory and runtime model isn't suited for the requirement of the tool, and language doesn't allow for a paradigm that matches well with the problem domain... You've picked the wrong language.