Async/await is a great example of things I wouldn’t be doing — or at least not doing that way — in JavaScript. MAYBE server side it might serve some utility, but please for the love of Christmas keep that away from the client side.

All of this nonsense strikes me as people doing things in JavaScript that fall into one of these three categories.

  1. Are none of JavaScript’s business
  2. HTML or CSS could handle without scripting screwing things over
  3. Would be less code, simpler code, and more efficient/faster without these alleged “improvements”

It’s the same problem we see with these dumbass frameworks; where the entire thing is conceptually flawed and often goes against the intent of the related languages. Again, this is a bigger problem client-side where moronic chazerei like React, Vue, and Angular piss away graceful degradation and accessibility, whilst bootcrap, tailwind, w3.css, and all the other HTML/CSS frameworks piss on why HTML exists and what it’s for.

But right now? We’re seeing the same thing happening to JavaScript that happened in HTML 5… as many bad ideas introduced as good ones, new convoluted approaches and pointless redundancies trying to make up for deficient education, and a general reek of the people working on it now having failed to even grasp how to use what already was properly.

A situation exacerbated by people abandoning other languages like Java and the various flavors of .NET for node.js, then trying to make JavaScript work like those languages instead of embracing its differences. Hence why we end up with equally mentally enfeebled trash like LESS/SASS/SCSS, TypeScript, and all the other nonsense that could be avoided if people just took a moment to think about what they were doing instead of blindly hoping some “tool” will save their ass.

All of which — as I’ve said a thousand or more times the past decade — people could probably have avoided if they’d stop using 100k of HTML to do 16k’s job, 500k of CSS in a dozen files to do 32k in one file’s job, and 2 megabytes of “JS for nothing” on pages that IF they even need Javascript probably don’t need more than 64k of it in two files. (not counting social media plugins).

But no, that would involve embracing semantic markup, accessibility, usability, progressive enhancement, and actually having a graceful degradation plan.

Written by

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store