You old curmudgeon you... ;-) Make has it's foibles - before we talk about those we need to declare are we talking gmake, nmake, BSD make etc. - our build scri

You old curmudgeon you... ;-) Make has it's foibles - before we talk about those we need to declare are we talking gmake, nmake, BSD make etc. - our build scripts can break in the wrong make. And how will windows users collaborate (they'll install cygwin). Etc etc All that said though, I still find make to be lower barrier to entry. If I need to start a watcher or something, I generally have that in my npm package.json but there's nothing stopping me having a make target to call npm start or whatever. I forced myself to learn enough gulp to be dangerous (incidentally I see strong parallels between grunt / maven and gulp / gradle) and the faux pipes implementation is clearly influenced by make, it's just far more clunky an implementation. So it could just be I'm wired up wrongly but I have to agree, neither grunt nor gulp moved the needle meaningfully. Counter arguments like it's all one language don't hold much water for me, or for the designer who only really knows css. I'm resigned to being labeled a curmudgeon in this one!