After one of my team members sent my company's dev crew this link the other day, I decided to spend some time this weekend incoprorating Sass into my workflow for an upcoming web app.
As my spoilers in the title indicate, I have now decided that my team is going to be required to use these tools. There was initially, not a lot of resistance, but just a plain lack of interest in these tools at my company. All but one of us really didn't feel much push to start using a tool that we felt saved us very little time and could possibly screw up our workflow.
Well, here I'll say that I was wrong. Sass is excellent and I'll just bullet point this:
- I can continue to use CSS the same way as before, especially with automated compilers. There are other tools like CoffeeScript that yeah sure I type less, but now I can't work in JS.
- It's intuitive as hell. I only spent a little time with the documentation and the code was doing exactly what I expected even when I simply guessed its style.
- Sass allows me to have a base variable to store things like color definitions in one place. Now if only I could get object classes in Sass.
For me, the biggest issue was that Sass meant processing got added to realm that previously didn't have it. Processing adds complexity, which adds the likelihood for bugs. The reason this doesn't matter is that CSS is already pretty screwy in that small typos already completely fuck up entire sheets, and the processing with Sass is so low level that anyone who has programmed for a shortwhile won't be confused by method.
The biggest point is that Sass is tooling done right - turning a shorthand into actually workable commands within the existing CSS framework. Other modifiers tend to force your hand to only work in shorthand, but as a coder, you want both availble. Sass does exactly that. So if you don't work for me, you may not be required to use Sass, but I would recommend you try it.
Monday, June 24, 2013