Why did many developers abandon Grunt and switch to Gulp?

Question

JavaScript

Greetings to anyone who answers the question! And one more thing is interesting, what is the point of using Grunt or Gulp if you basically don’t work with the console, but use an IDE where support for all auxiliary tools is already built in or added through plugins, it’s enough just that the necessary utility is installed in the system? Well, here's an example. I used the following tasks when testing Grunt: csscomb, sass, concat, uglify, clean, imagemin, browserSync, watch. All this can be easily configured in VSCode...

Answer 1

They switched from grunt to gulp because he was able to parallel tasks and was faster due to this.
Building assets through the IDE is not used for a number of reasons:

1. It doesn't work on CI/CD
   
2. Not everyone uses the same IDE
   
3. Even if they do, setting it up for every team member is a waste of time. The task runner config is written once for everyone, and if the build pipeline changes, you only need to change it once.
   

Now neither one nor the other is relevant - look towards webpack, parcel and rollup.

Answer 2

Why not just google the question? There are a lot of ancient articles on this topic, because gulp is now outdated, read about webpack or parceljs
www.creative-seo.ru/blog/grunt-vs-gulp
And why? It all started with CI / CD and ended with the unification of the process.
In your case, you are tied to the IDE configuration, but what if a lot of people work on the project?

Answer 3

But what if you need to build a site from several locales, you can write the logic in the task runner and the template engine will do its job. Plus, Gulp is a task runner, which allows you not only to collect files, you can even set up publishing to the server, etc.
Well, why Gulp .