- From: Sebastian Zartner via GitHub <sysbot+gh@w3.org>
- Date: Thu, 17 Mar 2022 08:01:10 +0000
- To: public-css-archive@w3.org
@LeaVerou wrote: > While I agree that @Marat-Tanalin's comment was out of line, it really is not helpful to the discussion that every comment that @nex3 leaves here (and previously in the TAG repo) is announced on Twitter via the @SassCSS handle, urging people to flock to the discussion or else doom will come to their stylesheets. I totally agree with that. > That said, I don't think the `@If` workaround is a viable path forward. Many other paths forward have been suggested in this thread (`@-sass-if`, a global switch, etc), but the Sass maintainers do not seem to even be interested in discussing a win-win solution to this. @nex3's comment saying "I haven't read through this entire thread, but..." and Twitter posts do indicate that. Though I hope this can change. So please let's all calm down and try to have an objective discussion instead of fighting each other! Some people here in this thread including me were proposing ways forward for both, Sass and CSS. We've heard a lot of opinions on them by the CSSWG people but I'd like to hear concrete answers from the Sass people on whether those suggestions are good or bad in their opinion. @simonbuerger wrote: > @SebastianZ that doesn't solve the backwards compatibility issue, but it does solve the library compatibility issue (ie just a Sass upgrade is needed and third party tools don't need to do anything). Yes, it doesn't solve the backwards compatibility issue, though I consider requiring Sass users to update their Sass version if they want to use the CSS internal `@if` and the Sass developers to adopt the new syntax as a fair requirement and the least painful hurdle to let CSS use `@if`. > However it will be highly confusing and unintuitive for users so a change in Sass syntax should also accompany it (but can continue to support old Scss `@if` alongside in this scenario for a long period?). This might be the case. Though again, when the Sass change ships this could easily be answered by pointing people to the newest Sass Version. That's also why I agree with @astearns that we should give Sass developers the time to adjust before shipping this feature. > Not sure if the current Scss parser can be adapted to support differentiating the syntax like this That's why I wanted @nex3's opinion on that. Sebastian -- GitHub Notification of comment by SebastianZ Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6684#issuecomment-1070506005 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 17 March 2022 08:01:21 UTC