Why you shouldn’t create a gulp plugin (or, how to stop worrying and learn to love existing node packages)
I’ve been experimenting with the gulp task runner for a week or so now. My goal has been to recreate some or most of the functionality of ngBoilerplate's Grunt-based build script. (Confused? Look at the bottom of this article for some more information about all these terms.)
One of the biggest concerns surrounding the project is the very opinionated design, and view that plugins for it should be extremely simple. I wasn’t in total agreement with this philosophy until today.
I want explain why you should resist the temptation to write a new plugin for everything you want to use gulp for.