- From: Simon Buerger via GitHub <sysbot+gh@w3.org>
- Date: Wed, 16 Mar 2022 06:58:11 +0000
- To: public-css-archive@w3.org
Seems to me like avoiding pissing off a large portion of your user base (developers and open source maintainers alike) is a perfectly reasonable justification for choosing a different syntax 🤷♂️ Even if that syntax is slightly less favourable. Not sure it's even as cut and dried as you all think that `@if` is the better choice either. Even without this Sass discussion I think you'd still find a lot of support for `@when`. Probably more for `@if` certainly, but honestly the vast majority of end users and maintainers simply won't care at all. They'll use whatever syntax you decide here and not think twice about it. I certainly wouldn't care one way or the other without the Scss impact. Both seem perfectly clear, usable and justifiable. But if you choose `@if` (which you pretty much seem to have decided on already?) it will cause me some pain in the future, and that I really do care about 😛 Anyway I doubt I'll be changing any minds at this late stage so as you were I guess @daKmoR that looks reasonable, but I think the impact on third party libraries would still be high? Not sure how you'd handle for that where the libraries all use `@if` extensively - force them to all update to `@scss-if`? But then some libraries might not be actively maintained, and even if they were they'd lose backwards compatibility too... Or the maintainers would have to keep two concurrent versions to support pre-if and post-if versions of Sass. None of this sounds fun to me... -- GitHub Notification of comment by simonbuerger Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6684#issuecomment-1068798597 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 16 March 2022 06:58:12 UTC