Re:Build Wars: Gulp vs. Grunt
by 1971genocide on Monday September 29, 2014 @09:08PM
(#8386252)
I find any build automation tool to be a hassle. Tools like Gulp and Grunt remind me strongly of Visual Studio and C++, something I hope not to have to see on my screen.
I find using system calls to be much easier. Node.js has a really powerful API that most people seem not to want to use, rather then want someone to write a plugin to do their tasks for them. I understand being lazy is good in programming but build plugin is just overengineering in my limited experience.
Re:Build Wars: Gulp vs. Grunt
by mikegioia on Monday September 29, 2014 @09:13PM
(#8386267)
The thing with Gulp is that it can just be a simple wrapper to your node system calls. I use it just as a task runner to lessc files together, or run a browserify script, etc. It also really takes some pain away from piping data to different handlers.
Also, this might be an old slide. The spec this was referring to appears to be dead: https://github.com/node-task/spec/wiki
Btw there's also brunch (http://brunch.io) that you might want to check out. That one really does need only minimal configuration.
I wrote an article about all three not too long ago: http://blog.toggl.com/2014/03/grunt-vs-gulp-vs-brunch/
Edit: On Mac Chrome 37.0.2062.124, for what that's worth.
I find using system calls to be much easier. Node.js has a really powerful API that most people seem not to want to use, rather then want someone to write a plugin to do their tasks for them. I understand being lazy is good in programming but build plugin is just overengineering in my limited experience.