Gulp is an interesting idea, but I'm skeptical of its long-term viability. As Wintamute said in another thread, large projects have a lot of needs, and streamin

Gulp is an interesting idea, but I'm skeptical of its long-term viability. As Wintamute said in another thread, large projects have a lot of needs, and streaming isn't enough for all (most?) of them. Gulp's creators were pretty adamant about not supporting other use cases when this came up on Twitter. [1] Another issue with Gulp is that it's highly concurrent. Although that seems like a nice idea for speed, I suspect it will lead to a lot of hard-to-write and hard-to-debug edge cases. I've already heard reports of people getting strange behavior from their Gulpfiles [2]. At this point, I'd take a "wait and see" approach with Gulp unless you like playing with build tools or if you really need its focus on speed. If you're looking for a good build tool for that lets you "just run JavaScript," I'd check out Jake [3] instead. And of course, Grunt [4] is the current leader for JS builds, thanks to its immense plugin library. If you're interested in a more in-depth review of Gulp, I have one here: [5] [1] The Twitter thread: https://twitter.com/funkytek/status/423762923421302784 https://twitter.com/funkytek/status/423762923421302784 [2] Somebody runs into strange behavior from Gulp: http://www.reddit.com/r/javascript/comments/1v4tez/bottom_line_right_now_gulp_is_too_focused_on_its/cep25ac http://www.reddit.com/r/javascript/comments/1v4tez/bottom_li... [3] Jake: https://github.com/mde/jake https://github.com/mde/jake [4] Grunt: http://gruntjs.com/ http://gruntjs.com/ [5] My Gulp review: http://www.letscodejavascript.com/v3/comments/lab/1#comment-1197581116 http://www.letscodejavascript.com/v3/comments/lab/1#comment-...