- From: Pierre-Yves Gérardy via GitHub <sysbot+gh@w3.org>
- Date: Fri, 18 Mar 2022 07:12:11 +0000
- To: public-css-archive@w3.org
@nex3 what about a new file extension? It would be equivalent to a per file compiler flag, and AFAIK authors can chose file names, unlike build pipelines that may be beyond their purview. Assuming the WG agrees to reserve some syntax for server-side extensions that gives us : - official recognition for the value of server-side preprocessors - no more future clashes, both the WG and preprocessors could innovate without stepping on one another's toes (e.g. `/` could mean division within a `-calc()` expression. You could thus keep the "superset" promise forever, no pleading required - better readability. Having distinct syntax for server- and client-side logic would make it clear what happens where, especially for beginners who don't know enough Sass or CSS to tell apart which is which. @ai @matthew-dean @iChenLei What do you think of this ? -- GitHub Notification of comment by pygy Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6684#issuecomment-1072090158 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 18 March 2022 07:12:12 UTC