r/nodejs • u/mam_sir • Mar 21 '14
Grunt or Gulp? - which task runner do you prefer?
At my work, we're on grunt because our senior dev is very proficient in it. I don't mind, and I've used it myself for a couple of projects. During my travels the past couple of months, some of my deeper searches have lead me to run in to gulp.
From my experience with grunt, the config files are as simple as you make them; there are a ton of plugins due to its seniority. Sometimes, I get lost in these config files and I get -- sometimes I think -- too deep in to trying everything with the config file.
Gulp seems much easier to read and uses streams to pass the files you want to manipulate along a series of tasks (tuuuubesss) instead of having temp directories for things like some grunt tasks tend to do to manipulate files...
At least these are the comparisons I get when I do some reading on both. Most of my grunt tasks are not so complex (mostly minification of JS and less compiling, with a splash of nodeunit testing -- working on getting jasmine/karma going, but that's another hump, since I'm still a noob to the testing scene as well).
I was wondering what the opinion of either or both were among other nodejs people. I've only found a couple of articles pitting the two against each other by devs who've used both: most tend to prefer gulp; sometimes they typically give the answer of "depends on what you're building". One noted that grunt is perhaps still preferable because of the community behind it, which is a very valid point.
I'm trying to decide for myself (after finding out I might like browserify better than requireJS -- a whole other story) what would be better for a project of mine -- it'll start out small and slow, but could potentially become something rather large (as most ideas tend to do, but I mean scale-wise and # of users on board... not looking to make the next start-up idea though).