grunt takes an almost entirely declarative approach, which becomes really hard to reconcile with situations that the order of execution really matters. because you are basically trying to map a flat(ish) array of commands onto a tree-like structure to trick the grunt internals to work the way you need them to.

You can either do this explicitly (by setting up aliased), or implicitly (by all the temporary file watch jiggery and pokery).

It's unlikely that I will start any new projects with grunt, even though I know it a lot better than gulp right now.