> In my mind, SCSS + CSS modules + maybe a processor tool is an rock solid and modern set of tech
"my set of non-standard tools and preprocessors is superior to these guys' non-standard tools and preprocessors" is not a good argument.
> I find this reluctance to enforcing guidelines weird
Because CSS doesn't lend itself to any enforcement. All the tools that appear around it includng those you like like SASS and "some processing" don't appear because people don't understand something or can't enforce something.
> Of course, all this is under the hindsight knowledge that HTML and CSS have evolved in recent years to be truly powerful and versatile.
Indeed. And many of these features have been made available across all major browsers only in the past two or so years.
No one is going to rewrite everything from SASS or CSS-in-JS just because some features now exist in vanilla CSS.
I never said we have to rewrite existing apps and I explicitly mention that these improvements are recent. You come off as overly sarcastic and irritating in an otherwise civil thread.
"my set of non-standard tools and preprocessors is superior to these guys' non-standard tools and preprocessors" is not a good argument.
> I find this reluctance to enforcing guidelines weird
Because CSS doesn't lend itself to any enforcement. All the tools that appear around it includng those you like like SASS and "some processing" don't appear because people don't understand something or can't enforce something.
> Of course, all this is under the hindsight knowledge that HTML and CSS have evolved in recent years to be truly powerful and versatile.
Indeed. And many of these features have been made available across all major browsers only in the past two or so years.
No one is going to rewrite everything from SASS or CSS-in-JS just because some features now exist in vanilla CSS.