- From: Marat Tanalin via GitHub <sysbot+gh@w3.org>
- Date: Tue, 28 Sep 2021 23:08:53 +0000
- To: public-css-archive@w3.org
@vrugtehagel > If JavaScript introduced `Array.prototype.flatten`, my site would break without my knowledge, even though I didn't touch it. This negatively affects users. If CSS introduced `@if`, then... well, nothing. I already built my CSS 5 years ago, and my CSS (the output) didn't use `@if`, so that's all good. My SCSS build may fail, but that's irrelevant; my site didn't break for its users. Basically, the difference between breaking something for a JavaScript library versus breaking a CSS preprocessor is that the latter doesn't directly impact users of the web, while the first may break many unmaintained sites when released in browsers. 👍 > SCSS is, in a way, more "temporary" and easier to change than CSS itself, so there could be a time where SCSS slowly dies out (perhaps because CSS itself became feature-rich enough for most developers) and by that time we're stuck with a less intuitive `@when` rather than just `@if`. 👍 -- GitHub Notification of comment by Marat-Tanalin Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6684#issuecomment-929688600 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 28 September 2021 23:08:54 UTC