Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I use SASS on Windows with no issues and it was rather easy to get up and running. Granted it did require the installation of Ruby of which I only use it for this, but that's a small price to pay.


Indeed. IMHO the concerns expressed by some here about relying on Ruby are greatly exaggerated.

For anyone who is curious, the steps required to use SASS on Windows are something like:

1. Download RubyInstaller from rubyinstaller.org and run it. (This is a self-contained Windows installer for Ruby and the related tools/documentation.)

2. Run "gem install sass" at a command prompt. (This downloads and installs SASS itself, including SCSS.)

Personally, I'd love it if Ninite picked Ruby up as an option, because I already install many other tools that way in a single step. However, installing Ruby manually is no harder than installing any other piece of Windows software you download, and installing SASS on top is literally a one-liner.

Unless you're developing on a relatively old and low-powered system, I don't see any downside to having the extra software installed either: it's just another tool, occupying a few MB of hard drive and a few characters in your PATH, and IME it's perfectly friendly toward development toolchains for other languages.


Your two-part explanation is accurate. The Sass team was nice enough to even point you to RubyInstaller right there on their download page.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: