- From: Natalie Weizenbaum via GitHub <sysbot+gh@w3.org>
- Date: Thu, 30 Mar 2023 23:51:53 +0000
- To: public-css-archive@w3.org
> PostCSS Nesting for example has ±7 million weekly installs. Whereas Sass has about ±11million. Note that Sass's npm distribution is not the whole story—Sass is also commonly installed via Homebrew, Chocolatey, GitHub downloads, the occasional Linux distro, and so on. Sass's support for `&foo` is also much older than `postcss-nesting`'s (Sass added support in 2014). On top of all of that, using `&foo` as a suffix is likely to be _much_ more popular among Sass users than using it to add a type selector is among `postcss-nesting` users: `&-suffix` is a critical part of BEM-style design methodologies that use modifiers of base class names to communicate semantic relationships, while needing to add a type selector to a compound selector in a nested context is so rare that we only had a small handful of support requests about it in the entire lifetime of Sass. It's also worth noting that Less (~5 million weekly installs on npm) and Stylus (~3 million) both also use Sass's semantics for `&foo` here, and have also done so for around a decade. -- GitHub Notification of comment by nex3 Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8662#issuecomment-1491104803 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 30 March 2023 23:51:55 UTC