javascript - How is glup better than grunt?

I just learned grunt and I feel it is already great. However, there seems to be a lot of comments on the Internet about how good glup is and how rubbish grunt is. I don’t think so. I think grunt is pretty good and the configuration file is not that complicated to write. Not all of them. Complete some basic automation work? Is it a waste of everyone's time to do so much?

Reply content:

I just learned grunt and I feel it is already great. However, there seems to be a lot of comments on the Internet about how good glup is and how rubbish grunt is. I don’t think so. I think grunt is pretty good and the configuration file is not that complicated to write. Not all of them. Complete some basic automation work? Is it a waste of everyone's time to do so much?

Thanks for the invitation!
First of all, let’s start with your personal situation: You have just learned grunt and have just come into contact with it not long ago, which means you are not very familiar with it. When you first came into contact with it, you thought it was good because of freshness, curiosity and other reasons. It is recommended that you take a look at it for a while, wait until you are familiar with it, see if it is suitable for the development of your own project, and then consider whether to change to another one. Most of what we know about glup is based on the experience of some seniors, so it doesn’t hurt to take a look. There are specialties in the art industry, so be good at one first.
I personally feel that sometimes grunt consumes a lot of memory. This is my most profound experience using grunt, and I am currently using grunt. Hope the answer is helpful to you

It’s all automated, what to do with the time saved? Just stand in line again...(error)

I used grunt before, but later switched to gulp.

I think gulp is more code-oriented and easier to read.

Tell me about your own experience of using it

• gulp's configuration file does not have so many parameter configurations, and it is based on the unix pipe idea, which makes people feel very comfortable when writing build task codes, which is more conducive to maintenance and reading by developers

<code>gulp.task('sass', function() {  
  return gulp.src('src/styles/main.scss')
    .pipe(sass({ style: 'compressed' }))
    .pipe(gulp.dest('dist/assets/css'))
});</code>

• gulp’s API is simpler and easier to use

• gulp's node-based streaming can quickly build projects and reduce frequent IO operations

First of all, the emergence of a new competitor must have grasped the pain points of the old man.
For beginners or those with little experience, you will definitely not feel anything at first~

And for a newbie like me who has never used anything, I don’t know what to answer.