|
I'd wager that most of the developers who build modern websites and web apps don't start off thinking…
Most of the time, I hear stuff like…
And yet, so many of the sites and apps we use today are slow, buggy, and hard to maintain. Why is that? Let's dig in! If we're using tools that reduce complexity for us, why are the things we're building so damn complex?Part of it is that we're sometimes building things that are, frankly, more complex than websites and web apps were a decade ago. But for the most part, we're not, actually. The web is still mostly just forms and links, with occasional islands of complexity. But tools like React are compounding. Like a cancer, the spread to everything around them, consuming a site and destroying it in the process. React infects everythingWhen you're already "paying the React tax" for a component or two, there's a tendency to just grab a React component for this new thing you're going add, or this piece of your app you wanted to update, or for the whole damn thing, even when it's just a blog or marketing site. And while React (allegedly) makes some things easier, it also makes some easy stuff a lot harder. It creates a giant dependency tree. It requires a complicated build process. It slows down your whole site. It creates a worse experience for your visitors. Stopping complexity creepThe best way to fight this effect, frankly, is to not let React and it's ilk into your code base at all. Because once you do, it spreads. You can't stop it. When I audit client sites for performance or maintainability issues, one of the most common culprits I find is React. If you need help simplifying your tech stack, or want to make sure you build your app right from the start, get in touch. This is what I do! Cheers, Want to share this with others or read it later? View it in a browser. |
0 Komentar untuk "[Go Make Things] Compounding complexity in modern web development"