When comparing Gobble vs Broccoli, the Slant community recommends Broccoli for most people. In the question“What are the best Node.js build systems / task runners?” Broccoli is ranked 8th while Gobble is ranked 14th.
Ranked in these QuestionsQuestion Ranking
Using Gobble is even easier when you consider the fact that it's extremely debuggable.
Pro Very easy to write plugins
Gobble's API is very easy to learn and very intuitive. This makes it very easy for developers to write different plugins for tasks that they may need.
Pro Brocfile fairly straightforward and small
Pro Rebuilds are really fast
In larger apps rebuilds get slower and slower as the size of the application increases. Broccoli deals with this by building only the files that were changed and intelligently figuring out their dependencies. This leads to rebuilds being of O(1) constant-time (in Software Engineering terms).
Pro Chainable plugins
With broccoli developers can chain plugins.
var tree = broccoli.makeTree('lib') tree = compileCoffeeScript(tree) tree = uglifyJS(tree) return tree
Con Still in active development
Since Gobble is still in active development it's API may change and it's documentation is not fully ready yet.
Con Windows not fully supported
Con Assumptions about your project limit what you can do
Assumes you want to always output to single output directory. This directory must not exist at the time of running. It also (therefore) can't be your current directory. This puts broccoli slightly out of the class of a truly general "task runner".
Con Small community
Broccoli's community is still relatively small and not very active, at least compared to it's competitors. This leads to fewer plugins, guides and less support from developers for any problem that you may face using Broccoli.