As a language, JS is what it is - therefore you can use or ignore parts of it, target it from a transpiler, etc. It's Node, its de-facto execution environment o

As a language, JS is what it is - therefore you can use or ignore parts of it, target it from a transpiler, etc. It's Node, its de-facto execution environment on the server side, that's the travesty - a hardly-glorified version of the browser's execution environment. Sure, a well-designed Node app. is better than your average long-running, thread-holding CGI script from 1998, but there have been servers for ages that can do async thread sharing/pooling like Node (and with proper language support, if you want it) but don't force you into this model if your task happens to require true task parallelism rather simple asynchrony, which require hacks that range from just ugly to truly horrid.