Just add native support for Sass and call it a day.
SASS encourage developers to build long chains of selectors and it makes them brittle and non-reusable.
CSS Variables landing in Chrome 49
21–30 of 70 posts
Re: CSS Variables landing in Chrome 49
#22For those commenting about SASS having this forever etc, note that this goes a step further:
:root { --color: blue; }
div { --color: green; }
#alert { --color: red; }
* { color: var(--color); }
In fact, this feature isn't even covered with cssnext:
The current transformation for custom properties aims to provide a future-proof way of using a limited subset (to top-level :root selector) ... [1]
[0] https://developers.google.com/web/updates/2016/02/css-variab...
Re: CSS Variables landing in Chrome 49
#23Earlier quoted context omitted.
Pretty sad that in a world with living standards and silent updates, things that improve the state of the Web so vastly for developers still take so long to be widely available. (W3C doesn't even have a CR yet.) Less and Sass are nice, but the resulting CSS is full of repetition, thus hurting performance. Am I right in assuming that IE won't receive any more feature updates? Many enterprises will stay on Win 7 for a…
Given that Edge has pretty much completely replaced IE, then yes, it's unlikely IE will receive any more updates. And to make it worse, Microsoft doesn't seem to be updating Edge as much as they were promising, meaning that we could end up in the exact same situation as before.
Edge is an evergreen (ie auto updating) so it's a very good thing that MS is aggressively pushing to kill IE. In the not-so-distant future, IE won't exist.
Safari will likely be the next browser that will be slowest to update, considering its current progress in relation to the latest standards. Even with regular updates they seem to be falling behind.
Re: CSS Variables landing in Chrome 49
#24Earlier quoted context omitted.
The CSS team has people like this, who no longer make websites: https://www.w3.org/People/Bos/CSS-variables Thus they're disconnected from current web developers. Meanwhile Smashing says something like 77% of audience uses SASS.
Didn’t Firefox have actual SASS support for some time? I think at least the dev tools had support for SASS source maps, but I’m not sure if the browser actually had support.
Source maps aren't specific to SASS; you can use them with any tool.
Re: CSS Variables landing in Chrome 49
#25Earlier quoted context omitted.
Given that Edge has pretty much completely replaced IE, then yes, it's unlikely IE will receive any more updates. And to make it worse, Microsoft doesn't seem to be updating Edge as much as they were promising, meaning that we could end up in the exact same situation as before.
Edge is an evergreen (ie auto updating) so it's a very good thing that MS is aggressively pushing to kill IE. In the not-so-distant future, IE won't exist. Safari will likely be the next browser that will be slowest to update, considering its current progress in relation to the latest standards. Even with regular updates they seem to be falling behind.
> aggressively pushing to kill IE. In the not-so-distant future, IE won't exist.
Well, Windows 7 and 8.1 will receive support until 2020 and 2023 respectively. That gives us at least four years of IE 11 being the "new IE 6." (Yes, that is a bit of an overstatement, I remember the horrors of IE 6 quite well. It's still disappointing.)
Re: CSS Variables landing in Chrome 49
#26I've wondered for years why we're using pre-processing to get variables into CSS. Given that there hasn't been a commonly advocated workflow that didn't include some sort of CSS processor (like LESS or SASS) in about a decade, it seems like somebody working on the standards would have realized that CSS needed variables, at the very least. So, it's cool that it's coming, though it's taken a lot longer than I reckon it…
The CSS team has people like this, who no longer make websites: https://www.w3.org/People/Bos/CSS-variables Thus they're disconnected from current web developers. Meanwhile Smashing says something like 77% of audience uses SASS.
> Very few people (only professional designers, it seems) write style sheets longer than a hundred lines.
Hahaha, wow.
Re: CSS Variables landing in Chrome 49
#27Ok, that's cool. How long until we're able to use this and not have to worry about browser incompatibilities?
[deleted]
Re: CSS Variables landing in Chrome 49
#28For those commenting about SASS having this forever etc, note that this goes a step further: :root { --color: blue; } div { --color: green; } #alert { --color: red; } * { color: var(--color); } You can't accomplish that with SASS today. More info [0]. In fact, this feature isn't even covered with cssnext: The current transformation for custom properties aims to provide a future-proof way of using a limited subset (to…
Don't forget that CSS Variables can also be used within media queries.
Re: CSS Variables landing in Chrome 49
#29Why don't they just natively support realtime compilation of SASS/LESS?