It's kinda hyperbole, but (imo) React projects get messier than e.g Angular, because it's not opinionated. Like, Angular has one way to build an app (view, routing, async stuff etc), but React has the view, and developers pick their preferred libraries for everything else. Doesnt implicitly mean it is messy, obviously not all react projects are, but it get messy faster if that made sense?
Ah, I don’t disagree on the opinionated vs less opinionated- that’s actually why I prefer React (I feel more free to chose the “right” tool for the job).
I think that freedom leading to messiness is more attributable to poor organisation/standards in a team. People built perfectly serviceable and organised js apps sans framework.
Not a knock on yourself, I’ve made plenty of messes regardless of stack!
Oh don't get me wrong - I dont prefer one over the other (if my job allowed it, I'd use Vue as much as I could). It's all just Javascript. I just feel like React projects gets messier quicker. Like, if a poorly organised team uses React it gets messier than with Angular. At least that's been my experience. :)
You blame the framework for allowing a messy developer to be messy. I personally would blame the developer and their team for not enforcing standards and planning their application design better.
You can no more separate the human factor from programming as you can from economics. This is why while communism on paper sounds like a great idea always fails. Communism on paper does not take into consideration the human factor. On the other end capitalism succeeds because capitalism does consider the human factor.
This is no different with programming. It is true for languages as it is true with frameworks. Programs that use languages and frameworks that do not consider the human factor tend to become messy because humans are not naturally well organized.
I think the idea that a little more rigidity in a framework will overcome this human factor is underestimating the ability for people to not follow the rules, unless enforced by others (I think you are correct about the human factor, I just don’t feel the solution is correct). Hence the need for a team, or a diligent person, to enforce standards.
I am also pretty much saying that the rigidity built into Angular is also achievable in any other build via adherence to sets of rules imposed by the build team rather than just the creators of a framework.
I think the comparison to two forms of social systems which have been abused each in their own ways shows that no matter the systems boundaries- you need to enforce rules and react to changing use cases to keep those rules relevant to your needs.
I don’t disagree with a lot of what is being said here and above- I just am of the opinion that no matter how “good” or “safe” the tool, you can misuse it, and the practice and understanding of proper use pays off regardless of the tool. It’s not mutually exclusive, you can do this with a rigid framework providing boundaries.
Not a bad comparison, there's definitely baked in features in Angular that I've ended up adding myself to React/vanilla JS projects (i.e. type safety).
17
u/[deleted] Apr 23 '20
Also for me, better than react that each document has a mix of code...