// , “It is not so important to be serious as it is to be serious about the important things. The monkey wears an expression of seriousness... but the monkey is serious because he itches."(No/No)
Do you foresee any risks (beyond @import deprecation) to adding a namespacing system and private members to CSS compilation like this?
Also, when I read the title of this post, I thought of "Sass" in a different way, because only the first letter was capitalized. If anybody want Sass in a more literal (as in "Sassy") form, as a service, and will excuse a terrible pun, there's always FOaaS: github.com/tomdionysus/foaas
I think these are great changes that enable greater control over our libraries and modules. I don't see any risks. I just hope that developers will be on-board since these changes are very different from what we are used to with @import.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Do you foresee any risks (beyond @import deprecation) to adding a namespacing system and private members to CSS compilation like this?
Also, when I read the title of this post, I thought of "Sass" in a different way, because only the first letter was capitalized. If anybody want Sass in a more literal (as in "Sassy") form, as a service, and will excuse a terrible pun, there's always FOaaS: github.com/tomdionysus/foaas
I think these are great changes that enable greater control over our libraries and modules. I don't see any risks. I just hope that developers will be on-board since these changes are very different from what we are used to with @import.