When comparing Brunch vs Gobble, the Slant community recommends Brunch for most people. In the question“What are the best Node.js build systems / task runners?” Brunch is ranked 5th while Gobble is ranked 12th. The most important reason people chose Brunch is:
According to speed benchmarks, Brunch is one of the fastest tools around for compiling files. According to the authors of Brunch the reason behind this speed is that it recompiles **only** the changes that were made to an app and performs extensive caching of the app's code.
Ranked in these QuestionsQuestion Ranking
Pro Compilation is super fast
According to speed benchmarks, Brunch is one of the fastest tools around for compiling files. According to the authors of Brunch the reason behind this speed is that it recompiles only the changes that were made to an app and performs extensive caching of the app's code.
Pro Time to setup is extremely low
After installing Brunch the next step is to load a skeleton from git.io/skeletons. This step is as easy as installing another plugin from the npm registry, just point Brunch to the path of the required skeleton/generator then wait for it to work out its magic. Next, run
brunch build then wait for a second or two and voila! the project is ready.
Pro The configuration file is small and the configuration itself is fast and easy
Brunch's config files can be extremely small compared to other alternatives. The fact that brunch also allows you to chose from a number of generators also lowers the configuration time considerably.
Pro Concatenates scripts and styles and auto-generates matching source maps
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.
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.