|
I think React is objectively bad for most websites and web apps. But when I say that, one of the common criticisms I hear is "if you're not using a library, you're just writing your own with bad documentation." No. I'm not. But the undercurrent that's sometimes said aloud is that React gives your project structure, and forces developers to write code in a particular way.
They'll ask. No particularly, no. But I would happily take that over the React spaghetti code I see. Because the reality is, you can right spaghetti code in any language or library. I've seen tons of spaghetti React, and it's even harder to detangle and reason about then spaghetti jQuery. React itself helps drive this problem. At least jQuery's API was consistent. React has changed it's approach to writing code and managing state multiple times. Each one is a dramatic divergence from the previous way of doing things. Code bases that have been around for a while now have two or three ways of managing their UI, often layered with additional idiosyncrasies caused by different devs adding their own preferences to the code. I've heard this referred to as Lasagna Code: it's like spaghetti code, but with layers. If you suffering from this problem in your code base, get in touch. I specialize in helping organizations move and grow faster by reducing the complexity of their tech stack. Cheers, Want to share this with others or read it later? View it in a browser. |
0 Komentar untuk "[Go Make Things] React myth: React gives your code more structure"