- From: Romain Menke via GitHub <sysbot+gh@w3.org>
- Date: Thu, 03 Nov 2022 17:40:09 +0000
- To: public-css-archive@w3.org
For starters, I personally like the syntax of proposal 3 on principle. I would like it even more if we could omit `&` everywhere. It is just more consistent. I like it because it gives authors more options: - you can write `&` everywhere - you can use a linter to even enforce `&` everywhere - you can omit `&` everywhere I do not have strong opinions about nesting itself. For me nesting is a minor feature and should not dominate the language. This for context because it has been pointed out that I apparently have strong feelings about all this and that I oppose the syntax change. I do not. I will miss `@nest` blocks but not that much. I thought they were an elegant "catch all" solution for writing nested CSS. Something you truly do not have to think about, it just works. ----------- This as a prelude to say that I don't have an issue with the substance of this thread. I do however have an issue with how this all played out. I don't think it is ok to have a one sided discussion were the arguments one side are always discarded. I definitely don't think it is ok to call out individuals and mark them as solely responsible for why we can't have a certain syntax. I think we can and must do better. These issues are not important enough for all this drama, none are. -- GitHub Notification of comment by romainmenke Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7834#issuecomment-1302457608 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 3 November 2022 17:40:10 UTC