4 ms·
A neat little css property aside, isn't the separation of concerns a cornerstone of web pages? Html - structure of the document CSS - appearance JS - interacti
by arvindamirtaa 6y ago
A neat little css property aside, isn't the separation of concerns a cornerstone of web pages?
Html - structure of the document
CSS - appearance
JS - interactivity
I could be wrong, but that's how I remember it. Is there an advantage to moving away from this fairly simple and unambiguous paradigm?
- k__ 6y agoSeparation of concerns is still seen as the way to go. People just have different opinions about what a concern is. It started with markup, styling, and interactivity. But many people think, this is a too technical perspective and software should be split up into non-technical concerns (i.e. microservices).
- deleted 6y ago[deleted]
- tannhaeuser 6y agoThis structure vs appearance dichotomy was added after the fact, though, since CSS came significantly later than HTML. It has been used as a (misguided IMO) narrative to defend CSS's complexity and redundancy and is partially to blame for HTML and the web ceasing to be a straightforward medium for simple publishing, seized by big media and ad networks.