You clearly have not worked with in a competent JS-based project. Literally none of your objections are valid except for the single-threaded nature of JS. Whic

You clearly have not worked with in a competent JS-based project. Literally none of your objections are valid except for the single-threaded nature of JS. Which is also not quite valid, given that .NET has async now, with all the same faults. > 3) It takes minutes to start! I hope you never have an emergency update that needs to go out right now! This clearly shows that: 1. "Just copy it" leads to messes that need sub-second deployments. Probably manual ones, because simply spinning up CI/CD and running the tests typically takes longer. Were you responsible for that CrowdStrike outage? 2. My JS project compilation takes 10 seconds from an empty directory to the compiled asset. > 5) NPM libraries are under constant churn. Just updating packages requires minutes of 100% computer power to resolve the dependency graph logic... which has changed. We're using PNMP and our library resolution takes seconds. > 6) In .NET land there's basically only two ORMs used: Entity Framework from Microsoft and Dapper from StackOverflow. They work fine. Someone at $dayjob picked "typeorm" for Node. Is it the best? Who knows! It's interesting that you think that not having choice of libraries is good. I guess that's OK when your worldview has shrunk down to the confines of MSDN, and you can't see anything outside of it.