task-runners

Differences between Grunt and Gulp

• The way you configure your tasks. Grunt is configuration-based. Gulp is stream-based.
• The way they run your tasks. Grunt runs the processes you want to execute in a sequential manner. Gulp tries to run them with maximum concurrency, meaning it will try to execute processes in parallel if possible.

Using stream, Gulp saves a lot time on disk I/O.

Looking at the workflows:

Gulp

Grunt

In the End

So, Grunt or Gulp?

Honestly, it depends on the situation and it’s up to you.

One isn’t better than the other. They’re the same type of tool that can do the same job. So it will come down to personal preferences.

However, Grunt config format is a mess. As for me, I choose Gulp!

References

• official - Grunt

• official - [email protected]

• official - Gulp Plugins

• Gulp - a good getting-started guide

• Gulp Cheatsheet

• Gulp vs Grunt. Why one? Why the Other? @Medium.com on Jan 7, 2015.

• Grunt vs Gulp - Beyond the Numbers on Jan 27, 2014.

• Grunt vs Gulp: Which Web Developer Automation Tool Should You Use?

• Introduction to Node.js Stream

• Automate Your Tasks Easily with Gulp.js

• Gulp - recipes

TODOS

What I learned is just build the code based on src directory, however, Gulp can do more, linting, uploading, continuous integration, etc.