Why is "gruntjs" task runner named "grunt" [closed]

Question

Usually, I believe, the name of a library or tool carries an interesting and insightful meaning or very witty sense.

For example, *phantom*js is about testing with a browser that behaves like a phantom.

gruntjs must be named for a reason, I hope, and I expected it's explained in their homepage, but no luck. Does anyone know why it is *grunt*js, not something else?

Answer 1

Borrowing from what have been already commented by @explunit, a "grunt work" is some boring and repetitive work. That explains their description in the Grunt homepage, as you state that have seen:

Why use a task runner?

In one word: automation. The less work you have to do when performing repetitive tasks like minification, compilation, unit testing, linting, etc, the easier your job becomes. After you've configured it, a task runner can do most of that mundane work for you—and your team—with basically zero effort.