- From: Rasmus Schultz via GitHub <sysbot+gh@w3.org>
- Date: Tue, 23 Jul 2024 14:56:54 +0000
- To: public-css-archive@w3.org
> The downside of the publicity this issue got is many people are parachuting into it and confidently asserting they can solve all the problems I'm sure you're not talking about me, because I wrote *in italics* "I'm not sure about this idea". I've been watching this thread for about a month, so I don't think I'm not parachuting in either. I don't know how CSS engines are implemented internally, and my idea might be totally unrealistic. I'm not a browser or language engineer, I'm only commenting as someone who has been writing CSS since the 90s. I'm just an end user, but you seem to agree that my opinion probably echoes that of most end users: > Believe me, we’d all LOVE to do `@if` and do it properly That's why, as said, I hope we don't push for this out of impatience - any web feature effectively becomes a permanent fixture of the platform for eternity. If we add a half feature with already well established drawbacks, the syntax and complexity better not get in the way of doing something different, in the future, that "we'd all LOVE", right? 🙂 -- GitHub Notification of comment by mindplay-dk Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10064#issuecomment-2245486637 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 23 July 2024 14:56:55 UTC