3 ms·

I credit gulp with finally making me 'get' streams, even though I had tangled with them before. It's API is one of the [1] biggest inspirations to code I write

I credit gulp with finally making me 'get' streams, even though I had tangled with them before. It's API is one of the [1] biggest inspirations to code I write nowadays and it also helped me come to grips with the fact that code > config in almost every eventuality. All of that said, webpack is so very far ahead of everything else in the field that there is almost no way I would use anything else. It also has the side effect of making gulp mostly unnecessary. Simple Makefiles or shell scripts just get me a lot further nowadays. [1] https://github.com/GraftJS/graft https://github.com/GraftJS/graft

bronson 12y ago
I had the same experience. Gulp is simple and beautiful once you get it. And it's so much faster than Grunt. Alas, at this point, my build needs are also being handled by Webpack. And, if I'm faced with something weird, I'd first try to solve it with a Webpack plugin. It's nowhere near as pretty as Gulp but it's the simplest to configure and most comprehensive. It's been a tumultuous few years for JS build systems...
hamburglar 12y ago
Was there any particular intro to Gulp that provided this revelation about streams? As far as I know, I 'get' streams, but now you're making me wonder. :)