3 ms·
"separations of concerns" is not about putting things in different folders or files. It is about those things not being entangled as spaghetti with each other.
by ralfn 9y ago
"separations of concerns" is not about putting things in different folders or files.
It is about those things not being entangled as spaghetti with each other.
Reacts Philosophy is that everybody's css/js/html is tightly coupled and therefor using different languages with different semantics and scoping rules increase the cognitive complexity without providing any advantage.
Can I break your app by just touching the CSS? Does any cosmetic change at any point require that I touch the html? Can I write a new style sheet for your app without knowing the JS or HTML? Can I plug in a new style sheet of one application into another? Can people work on the JS/HTML/CSS separately and independently?
Putting your spaghetti in separate folders doesn't make it less spaghetti.
And the market knows it's tightly coupled spaghetti for everyone. Thats why you don't see different job adverts for your three different folders.
The goal was to have a world where the designer would know CSS but zero JavaScript and zero HTML. This goal has completely failed.
- dkonofalski 9y agoI think web apps are a little unique because there's huge parts of them that are not content and that's where the separation of concerns originally came to be. I vehemently disagree with you that all of these things have to be entangled and tightly coupled. I think they just end up that way because it's the easy way to get through a problem and people who do things like that are, generally, lazy or on a tight deadline (for no reason that to have a deadline) or stressed or any number of things. Unfortunately, if all you're given is noodles, sauce, and meatballs, you're probably going to make spaghetti.