> and that's why that form of separation won out. React won out because it has a low barrier to entry and is very unopinionated. That's not a bad thing. But do

> and that's why that form of separation won out. React won out because it has a low barrier to entry and is very unopinionated. That's not a bad thing. But don't pretend for a second that it won out as any kind of industry standard because it was technologically superior or was a better designed "framework" (again, it's not and never was a framework, it's a view library for creating components). There are 3 broad concerns when it comes to programming for the virtual machine that we call the web browser: - Semantic demarcation, which is what markup does: this is a paragraph, this is a header, this is card etc. - Visual decoration and styling, what CSS does. This is how a paragraph looks, this is how a card looks etc. - Interactivity and control flow: what JavaScript does. When the user clicks the button this is what happens. Those are all distinct responsibilities which the browser handles separately natively. We don't need to even start talking about MVC or OOP design patterns when talking about spearating your concerns. That's a basic engineering concept of isolating your moving parts to keep things simpler and allow you to change things in isolation without acccidentally breaking something else, which is the bane of software maintenance. The notion that diluting separation of concerns is a design innovation that makes software development and maintenance somehow easier is truly baffling.