Drop the Ruby dependency about grunt-contrib-sass

[tkellen]

The way I envisioned (and implemented) the original contrib series was as monolithic set of official plugins. Eventually it became clear that they should each be their own individual project. When I broke them out into separate repos it was no longer an issue for some of them to have non-js requirements.

[JamesMGreene]

So there is no plan for grunt-sass to get merged into grunt-contrib-sass in the near future? If so, that's fine... I guess I'll just use grunt-sass instead. The allure of the "grunt-contrib-*" name brought me here first, of course.

[tkellen]

That would be a question for @sindresorhus--he maintains this repo.

On Apr 18, 2013, at 10:02 AM, "James M. Greene" [email protected]
wrote:

So there is no plan for grunt-sass to get merged into grunt-contrib-sass in
the near future? If so, that's fine... I guess I'll just use grunt-sass
instead. The allure of the "grunt-contrib-*" name brought me here first, of
course.

—
Reply to this email directly or view it on
GitHubhttps://github.com//issues/31#issuecomment-16581771
.

[JamesMGreene]

Ouch, GH mangled that email response.

@sindresorhus Thoughts?

[sindresorhus]

@JamesMGreene not in the foreseeable future. libsass (which node-sass uses) is missing a lot and node-sass has been nothing but trouble. This task is pretty stable now. If you want to take the chance on something faster, but more buggy and less features you can always use grunt-sass. But for most, stability and features are the most important things.

And why are you basing your "no Windows support" argument on a 7 month old closed issue.

[JamesMGreene]

@sindresorhus: I never said "no Windows support", just that it wasn't explicitly supported.

See this comment on sindresorhus/grunt-sass#7 (comment) for a little more detail.