Yesterday, Amy Hoy tweeted:
When asked what that meant, she elaborated:
pointless complexity, absurd tech churn, absolutely god awful tooling, a gnat’s willingness to commit to an approach, AND dicks.
And if you’re not familiar with the term gatekeeping, it’s the practice of actively restricting and controlling access to something.
Did I mention more tools?
A circular problem
The argument is that this tooling removes bugs, introduces structure, and helps eliminate errors introduced by junior developers.
There’s another way to do that, though.
A lot of what we rely on frameworks for can be done just as easily without one. A lot of what we use approaches like CSS-in-JS and code-splitting for could be handled just as easily by learning and embracing CSS and then writing less JS.
I’m not sure if all this modern absurdity is gatekeeping.
That implies a willful desire to exclude people, and the complexity crowd actually seems to want everyone to join them in complexity hell.
But, it does make the entire process wildly unapproachable to beginners. It makes code bases harder to maintain.
It makes websites and apps more fragile and less fault tolerant.
A way forward
It’s all unnecessary, and my professional mission is to show people a simpler way to make things for the web.