Naturally, a tool would come along to simplify and automate some of those processes. There’s a few major tools on the market, namely Codekit, Grunt & Gulp, that I want to break down a little bit.
The second offering of Codekit is even more amazing than the first. There’s a vast overhall done to it and is a lot more customizable, like it will let you execute bash scripts upon successfully compiling your code. It has a very interesting feature that lets you use includes in HTML through the Kit language that AJ Troxell explains very well how to use. Plus that server thing is pretty sweet; sometimes I use Codekit just for that feature.
The thing that grabs me most about Codekit is that it’s easy to get up & running with very little effort and you can only really tell it’s there when you’ve hit an error in your code. It just works. It fits in a workflow intuitively and sits very comfortably in the background.
As far as downsides, it costs money (but $36 isn’t a terrible price to pay for software you use all day). I’ve run into errors using Bourbon and Bourbon Neat because the Codekit versions of these libraries are still running on older versions of Sass. The only other thing is that if you’re using Grunt previously, it will try and automatically minify your Gruntfile and freak out.
Speaking of your Gruntfile, Grunt.js is a little more involved with the project you’re working on. It requires a good bit of configuration and setup but you get a lot more control and options. I like Grunt because you need to use the command line to get it going and it only runs tasks when you want it to, whereas with Codekit you have to tell it not to compile, concatenate, refresh, etc.
Grunt’s most appealing feature, by far, is the number of tasks you can configure and run. For instance there is a task that lets you set a pixel fallback to every rem declaration, and another one I love is a notifier that sends OS X notifications when you hit an error. There are tons of grunt tasks for a nice SVG workflow, like minifying those files and taking out all of the stuff Adobe Illustrate exports with it.
There isn’t really anything you can’t do with Grunt that you can only do with Codekit. It just requires more configuration. You can spin up a static server with Grunt, too, and you can choose the ports and every other detail. You can even use Grunt to compile Codekit’s Kit files.
I think my real allegiance to Grunt is that it got me to use the command line more and think about other tools like Yeoman and Bower. And it took me a while to get the hang of, no matter how many posts Chris Coyier wrote about it. It got me to think about my workflow and scrutinize and make me consider where I really needed to improve things.
Then there’s Gulp.js, it’s by far new and shinier than the other two build tools. I’m not really into Gulp yet. Based on this talk from Mark Dalgleish, I should and will love it but it needs to mature more. It is definitely on my radar though. I’ve watched a few videos on it and it feels like there’s less setup, and it’s easier to customize and get going with your project. I will be spending more time with it soon and will definitely share the results.
My basic thought on these build wars is simple: Codekit is for when you wanna get started, Grunt when you to really need to get into things indepth. The point of a good build tool is one you don’t have to think about; it simply fades into the background and lets you work.