This content originally appeared on Go Make Things and was authored by Go Make Things
I am consistently finding that React makes large code bases more unwieldy, not less.
It’s a pattern I’ve seen over-and-over again with multiple clients.
The same issues that React allegedly “prevents” over more traditional methods just get repeated, because those issues are people problems, not code problems.
- Repeating yourself instead of creating reusable functions.
- Code that’s hard to read.
- Lack of documentation.
- The same tasks handled multiple ways.
- Inconsistent authoring styles.
That all still happens!
Only now, because you’ve added this complex layer over your work, you also have to deal with…
- Code that’s harder to debug.
- Chasing errors through a deep dependency tree.
- Code that would be easy without a library but is hard because of quirks of how React works (for example, running code after the UI updates).
- Performance issues.
And this isn’t just a React problem.
React potentially encourages it more than some other libraries, but you can swap in Vue or Angular or whatever and these same statements hold true.
But none of these issues are strictly technical ones.
Fixing them requires establishing developer norms, then enforcing them through social conventions and pre-commit processes that catch issues early.
That’s not nearly as “wave a magic wand” as tools like React promise to be, but it is a lot more effective.
Like this? A Lean Web Club membership is the best way to support my work and help me create more free content.
This content originally appeared on Go Make Things and was authored by Go Make Things
Go Make Things | Sciencx (2025-03-17T14:30:00+00:00) Unwieldy code bases. Retrieved from https://www.scien.cx/2025/03/17/unwieldy-code-bases/
Please log in to upload a file.
There are no updates yet.
Click the Upload button above to add an update.