Here are some thoughts I had after reading through the slides and gist:
- I don't think I'd often use
*prop
. I don't keep track of which properties/values need vendor prefixes (or nonstandard code) to work with the browsers I'm targeting. I use Autoprefixer, which uses data from the Can I Use? database. - A command that generates JSON with keys representing the variable names used in a .gcss file would be handy.
- I feel like I missed the point of storing style variables in JSON. One benefit is "different site themes"--but most of my projects include a "_variables.scss" file that could be swapped out--oh, but that would require recompiling scss. I see. I think I get it now. Never mind!
I understand this point of view. A lot of people like autoprefixer. I think it has several downsides, not the least of which it's pretty hefty to run in-the-browser. I prefer the simpler and more explicit approach in this respect. But I appreciate the other side, too.
In that case, I'd say use a CSS templating engine but omit the
*
s, and then use Autoprefixer on the rendered CSS.