This is more of a question than an issue. Everything that stylus can do rework can be extended to do? Is there any exclusive benefit to stylus? I can't think of one other than more features right-now? What's your personal take on stylus, deprecated? I guess you could release a new version of stylus that is basically just a module/opinionated bundle of rework plugins ala Janus for vim?
I think my take on it is that less/stylus/sass etc. should all become opinionated bundles of rework transformations. Plus "preprocessors" to handle syntax extensions such as white space sensitivity.
I think assets maganers can add this preprocessors. We don’t need this support in Rework core.
@ai asset managers? Is this an "asset manager" https://github.com/visionmedia/css-whitespace?
@ai I don't think asset managers is quite the right place for them, but the likes of stylus/less etc. can add them without explicit support from rework. That's definitely an option.
@jasonkuhrt @ForbesLindesay I meen Assets Pipeline from Ruby on Rails, it compile templates based on file ext. I think that the best way to combine Rework with Stylus/Sass is to compile .sass/.styl to CSS and them process in in Rework.
Rework is just much easier to maintain, and faster by-design since it doesn't have an entire interpreter built in. The more we wrote stuff the less we used most of the interpreter, I'm not entirely convinced those are even good features, they really promote coupling, so I wrote rework to speed up our builds and only use what we actually need which is mostly just some nesting / css3 stuff
How are you planning to implement nesting? Are you going to extend the css parser?
css-whitespace has the nesting logic currently, but that should really be a second layer (or just another one for people that dont want significant whitespace)