I'm a software developer based in Newcastle Upon Tyne, England. I've got a wide range of experience in companies of varying sizes and cultures, and in roles of varying degrees of responsibility.
(I'm sure there are many more differences, it's been years since I've used either, as I'll explain below)
My personal preference is to use neither, and to create individual tasks in ("scripts" in package.json) for things that I might otherwise use a task runner for, with names that describe what they do rather than what tools they use.
The reasons for that preference are that:
I want to be able to change the implementation of those tasks without the people who actually use them (i.e. the other people that work on codebases that I work on) having to understand what they're doing under the hood - I don't want people to have to care what I'm using to minify files (for example), I just want them to know that if they use npm run minify then that's what it will do.
It means that anyone who is new to a Node project that I'm working on can look at the scripts section of package.json and see what options are available. This could be achieved with Gulp/Grunt too of course but it means doubling-up quite a lot in my experience.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Grunt runs tasks one at a time.
Gulp runs tasks all at once.
(I'm sure there are many more differences, it's been years since I've used either, as I'll explain below)
My personal preference is to use neither, and to create individual tasks in ("scripts" in package.json) for things that I might otherwise use a task runner for, with names that describe what they do rather than what tools they use.
The reasons for that preference are that:
I want to be able to change the implementation of those tasks without the people who actually use them (i.e. the other people that work on codebases that I work on) having to understand what they're doing under the hood - I don't want people to have to care what I'm using to minify files (for example), I just want them to know that if they use
npm run minifythen that's what it will do.It means that anyone who is new to a Node project that I'm working on can look at the
scriptssection ofpackage.jsonand see what options are available. This could be achieved with Gulp/Grunt too of course but it means doubling-up quite a lot in my experience.