- From: Sebastian Zartner <sebastianzartner@gmx.de>
- Date: Wed, 23 May 2012 05:44:05 +0200
- To: Sylvain Galineau <sylvaing@microsoft.com>, mtanalin@yandex.ru
- Cc: www-style@w3.org, jackalmage@gmail.com, brad.kemper@gmail.com
> On the other hand, if too few are using SASS for us to care then there > are no obvious usability benefits to matching their conventions and we > should move on. Or people simply don't know about SASS yet. E.g. I just heard of it last month. > > If something should be changed, it's SASS based on CSS choices, not > > CSS based on SASS choices (moreover, as far as I can recall, > > something like this has been stated by SASS author himself here in > > www-style list before). > > Who uses which syntax was not my point. My concern was that making CSS > and Certain frameworks depend on the same syntactical constructs may > not be such an obvious win; even from an education standpoint any > runtime difference is a possible source of confusion for the people > most likely to care about a common syntax: those who already use these > frameworks. So the fact that these frameworks have some traction is not > necessarily a good reason to imitate them. While I didn't use SASS so far I do not think it will cause such big problems. If SASS doesn't adopt CSS variables syntax, it will just continue parsing variables in it's own syntax and it's fine. Or it will adopt CSS variables and produce less code. The only disadvantage for SASS would be one point less on their features list. So people using SASS will continue using it and it will work. Sebastian -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de
Received on Wednesday, 23 May 2012 03:44:53 UTC