Cargo-Cult types notwithstanding, I think developers were mostly smart enough to interpret "separate the view from the code" to mean "separate the application logic from the presentation logic".
The problem that this project is trying to solve isn't that style and structure are too loosely coupled, but rather that declaring style in a DRY, high-level manner typically uses one language (e.g. LESS) and declaring structure in a dynamic manner often uses at least two more (HTML, JavaScript). Otherwise sane people have been known to use HTML, JavaScript, PHP, SQL, and a templating engine (and maybe another language or three for cron jobs and shell scripts).
If there's a weakness here it's that it's explicitly avoiding the concept of DSLs, which may or may not be a wise move.
Comments
Cargo-Cult types notwithstanding, I think developers were mostly smart enough to interpret "separate the view from the code" to mean "separate the application logic from the presentation logic".
The problem that this project is trying to solve isn't that style and structure are too loosely coupled, but rather that declaring style in a DRY, high-level manner typically uses one language (e.g. LESS) and declaring structure in a dynamic manner often uses at least two more (HTML, JavaScript). Otherwise sane people have been known to use HTML, JavaScript, PHP, SQL, and a templating engine (and maybe another language or three for cron jobs and shell scripts).
If there's a weakness here it's that it's explicitly avoiding the concept of DSLs, which may or may not be a wise move.