The State of JavaScript – Survey results
I apologize if the predictability of this comment, but I just want to say, I recently started a new gig at a company that has undergone a full on embrace of Javascript for tooling and server side projects and it boggles my mind how much productivity is wasted on this ecosystem. There is an interesting amount of energy put into making asynchronous code read synchronously in situations where asynchronous code provides no benefit. The dependency tree of any one project tends to be incomprehensibly sprawling. Runtime version numbering is... weird. Don&#x27;t even get me started on the interplay of Gulp, Grunt, Webpack and NPM. ES6 is bizarrely noisy. ESLint fascism is a necessity given the history of legal anti-patterns the language must shoulder. Scoping can occasionally lead to absurdist solutions [1].<p>I know this is the future and I&#x27;m trying to embrace it, but boy does it feel icky doing it.<p><a href="http:&#x2F;&#x2F;stackoverflow.com&#x2F;questions&#x2F;33629343&#x2F;what-is-the-best-way-in-es6-to-assign-a-constant-conditionally" rel="nofollow">http:&#x2F;&#x2F;stackoverflow.com&#x2F;questions&#x2F;33629343&#x2F;what-is-the-best...</a>