- From: Michael Mifsud via GitHub <sysbot+gh@w3.org>
- Date: Thu, 26 May 2016 10:55:42 +0000
- To: public-css-archive@w3.org
IMHO Sass is an incumbent technology, so purposely colliding with it is akin to "breaking the web". This issue ring similar to the [`array.contains` issue](https://esdiscuss.org/topic/having-a-non-enumerable-array-prototype-contains-may-not-be-web-compatible) faced by TC39. Sass will get out of the way as much as possible, but an `@if` like this could potentially force a python 3 style split that community. >What's the percentage? Hard to say for sure. A couple recent developer surveys put Sass usage at about 60%-70% of respondents. >preprocessors can always work around that easily This is generally true for when CSS does something new that preprocessors didn't previously do, like custom properties for example. However in the CSS of adopting an existing syntax there is no good work around for preprocessor authors. Best case they release a new major with a new syntax. Doing so breaks the existing community of packages. Even if all package were updated, there is always a significant percentage of people who cannot update for reasons like internal processes, or software. These users are affected the worse because they are left completely unable to use this feature. -- GitHub Notification of comment by xzyfer Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/112#issuecomment-221840086 using your GitHub account
Received on Thursday, 26 May 2016 10:55:44 UTC