Build Wars: Gulp vs. Grunt
markdalgleish.github.io
Build Wars: Gulp vs. Grunt
1–6 of 6 posts
Re: Build Wars: Gulp vs. Grunt
#2I 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
#3I 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 p…
Re: Build Wars: Gulp vs. Grunt
#4Edit: On Mac Chrome 37.0.2062.124, for what that's worth.
Re: Build Wars: Gulp vs. Grunt
#5Also, this might be an old slide. The spec this was referring to appears to be dead: https://github.com/node-task/spec/wiki
Re: Build Wars: Gulp vs. Grunt
#6Btw 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/