Because .js.<p>I think the general argument is this. Javascript is a necessary evil, but serverside, it isn&#x27;t. Please, let us use something saner, or at least give us the option to do so.<p>Javascript seems to be spreading into areas javascript has no business of being in, (&quot;node.js on microcontrollers? what?&quot;), and that is a bit disconcerting.<p>Granted, I&#x27;m fairly new to Javascript, but even  the good stuff seems like piecing together sane abstractions from wonky components. It&#x27;s the horror you&#x27;d feel if a nuclear reactor operator told you they get the components to go subcritical by grounding that bare wire next to their coffee cup. Does it work? Yes. Abusing function scope and closures to make variables private? Write a function that checks whether a variable is an array because typeof malfunctions? Does it work? Yes.<p>But then, is it sensible engineering? And even if you&#x27;ve gotten good enough at javascript that the gotchas simply seem kinky to you, do you really need it in every other area of your life?<p>I&#x27;m also be a little bit concerned that javascript will swallow everything else, and then the only way to program is to engage in a kinky whipfest, and whilst as a German I enjoy a good kinky whipfest, it&#x27;s really something for after work.