sass

SASS is almost a decade old [0] and has been in wide-spread use for a long time. The tool churning you talk of is something I have only seen in JS land to such a degree. Moreover, the barrier to entry to learning SCSS/LESS is really low if you know CSS. [0] https://github.com/sass/sass/tree/4acf5158734013f08fca4be6e2...

https://github.com/less/less.js 12k stars, yeah throw it out, it's done. https://github.com/sass/sass 6k stars, definitely more popular, if less stars means more popular. Obviously more front-end developers love sass! The evidence has spoken.

It's true. sassc(1) is a great step forward in terms of speed. That said, Sass encourages practices that I consider bad. Nesting, @extend, etc. Sass's design also makes it difficult to implement a basic feature like grouping all media queries for a single output. Check this issue from 2011: https://github.com/sass/sass/issues/116 If you don't mind a bigger tool and the dependency on Node.js, then PostCSS looks very good: https://github.com/postcss/postcss

I fell in love with SCSS on first sight and it has greatly helped me improve my front-end programming. From time to time I think of features that could make it even better. However, when I went to propose them I found that they are already proposed, like optional imports [1] and importing .css files (besides .scss) [2]. Some are closed, even though they are still planned for some point in the future. While I understand that it's a large project and it should be not easy to manage it, the date is from 2011 and 2013. Further investigation[3] shows that from 2007-2011, the top contributor Natalie Weizenbaum (nex3) was really active (~4k commits) in the site but now she seems to work for Google[4] on Dart. The 2nd biggest contributor made ~494 commits, or 10%. Third one made 40 or 1%. As a SCSS developer myself [5] I am interested in seeing S

Yes, the new [@at-root](https://github.com/nex3/sass/blob/master/doc-src/SASS_CHANGE...) directive. It is verbose but will allow you to extend root level extends. However this creates selector spaghetti in your CSS and should be avoided if possible.

I'm helping build Sourcegraph, which lists the gems that depend on FFI here: https://sourcegraph.com/github.com/ffi/ffi/network/repos/in and can show where some of its main methods are used: https://sourcegraph.com/github.com/ffi/ffi/symbols/ruby/gem/... and also for some other gems: https://sourcegraph.com/github.com/nex3/sass/network/repos/i... https://sourcegraph.com/github.com/lsegal/yard/network/repos... https://sourcegraph.com/github.com/rails/rails/network/repos... It would be great if someone added this functionality to rubygems.org (npmjs.org has it: https://npmjs.org/browse/depended/request). The Ruby support is very alpha right now. It works for some (but not all) popular gems, and it doesn't show transitive dependencies yet. Also, the list of dependents isn't comprehensive, but it should be a good starting point. If there are

In our current project instead of putting the framework's html/css into our codebase I'm outputting as bare bones html as I can with semantic class names on everything and then mapping those classes to the framework using sass mixins/extends/includes. To make a RWD site I'm having to rewrite a lot of the framework to be mixins instead of classes so that I can use them in @media as SASS doesn't allow @extend in @media any more[1]. What I'd find really useful would be a framework thats entirely built from mixins/partials and outputs no css until you create your own classes that use them. [1]: https://github.com/nex3/sass/issues/154 Disallow @extend within directives

Placeholder classes are new in SASS 3.2, so the blog post is explaining how to do them and what problem they solve. It's not unique, but it has been an awfully long time coming. See: https://github.com/nex3/sass/pull/236

If you watch the source here : https://github.com/Victa/path-menu/blob/master/sass/app.scss // Generate keyframes // Sass interpolation doesn't work with keyframe. CF : https://github.com/nex3/sass/issues/46 // so I use a tricks ==> "appear-'#{$i}'" - And it doesn't work in Firefox. It's impossible to generate @-moz-Keyframes + interpolation with Sass yet. That's why the experiment works only in Webkit.