It’s not a disservice when it fixes obvious flaws and issues. Flaws and issues that by their very nature are what the frameworks inherently create.

When the client needs scripting off graceful degradation to meet the “perceivability” part of the WCAG, how can I still use React, Angular, or Vue? When they’re having speed woes due to bloated markup and issues with non-semantic code, maintenance issues thanks to violating the separation of concerns, and codebases that reek of the worst of HTML 3.2 style thinking — thanks to the use of presentational classes replicating those FONT / CENTER tags, ALIGN / BGCOLOR / COLOR / SIZE / BORDER attributes, and tables for layout they all so dearly seem to miss — how the blue blazes can one advocate much less tolerate the PRESENCE of Bootcrap, tailwind, W3Fools “w3.css”, etc, etc, etc.

That’s when you have to tell the client to go find a stick to scrape the bootcrap off with so they don’t go tracking it across the Internet’s carpets.

They are not easier, they are not “better for collaboration”, they are not simpler, or better, and they sure as shine-ola aren’t efficient. They are a crutch for people ignorant of how to use HTML, CSS, or JavaScript client side, and are ALL clearly created by people who have no business telling anyone how to build a website. They take more time to create a template with, make slower loading sites thanks to bloated markup and missed caching opportunities, and flip the bird at usability and accessibility.

And the very methods of action by which they work — or even exist for — are at fault!

<starship troopers>Would you like to know more?</starship>

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