- From: Romain Menke via GitHub <sysbot+gh@w3.org>
- Date: Thu, 30 Mar 2023 21:07:38 +0000
- To: public-css-archive@w3.org
> One must also realistically consider the scale of the userbases between the projects. We're talking compat here, so actual number-of-devs-affected is more than a theoretical concern. PostCSS Nesting for example has ±7 million weekly installs. Whereas Sass has about ±11million. There are other projects like LightningCSS which adhere to the same principles and there are other distributions of Sass. Neither group is small enough to simply ignore :) There will be real compat pains here. > This is different from projects that intentionally followed our spec, intending to match what browsers eventually ship with - there was always the chance that the spec changes before browsers ship. (It's already happened once, with the removal of @nest and loosening of restrictions on selectors. Correct, we have and always will follow the specification. We might challenge proposed changes, but we will always follow the specification. This is the only thing makes sense long term. Any migration pains are short term. -- GitHub Notification of comment by romainmenke Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8662#issuecomment-1490964479 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 21:07:40 UTC