I’m not sure we’ve gotten much better at this since Tim Kadlec wrote this in 2012:

Stop me if you’ve heard this one before.

“Responsive design is bad for performance.”
“User agent detection is bad. Don’t segment the web.”
“Hybrid apps don’t work as well as native apps.”
“CSS preprocessors shouldn’t be used because they create bloated CSS.”

… Find out for yourself if the tool is really where the blame should be placed.

I’m sure there is some psychological concept that explains why we transfer blame from the offending thing to what we perceive to be the cause.

Sometimes we’re good at this. Remember the AMP letter:

The AMP format is not in itself, a problem, but two aspects of its implementation…

Or the fact that accessibility issues aren’t React’s fault. Pointing at the tools makes it harder to talk about the real problems that need to be resolved.

Sometimes I’m not so good at this. I’m linking to Tim here in an effort to help me remember this.

Direct Link to ArticlePermalink

The post Blame the implementation, not the technique appeared first on CSS-Tricks.