[bryanlarsen]

You definitely need a comparison with webpack. As far as I can tell from a quick scan, webpack has all of the capabilities that brunch does. More importantly, it's much more popular, so the plugins and help you need are likely to be available.

[graffitici]

I agree that Webpack is a serious competitor, and it's rather odd to not even mention it [1]. But I don't think Webpack does incremental compilation, since it usually takes quite a long time for me to compile my modestly-sized assets..

[1] https://github.com/brunch/brunch-guide/search?utf8=%E2%9C%93...

[bryanlarsen]

It does incremental compilation when run in dev server mode.

[ville]

I felt the same way. I'm already sold on the idea of using a proper build tool instead of a generic task runner (happy webpack user for 1.5 years).

Instead of telling why it is better than Grunt or Gulp, I'd like to know how it compares to webpack (or browserify, which seems to be quite close to webpack in functionality nowadays, http://reactpodcast.com/2015/06/webpack-vs-browserify/)

[pjungwir]

When I read about JS build tools online all I see is grunt/gulp, but when I talk to JS folks in person I keep hearing about webpack and how it does everything they need. Lately my frontend work has used ember-cli for all this stuff, but the next chance I get I'll give webpack some attention.

[wldcordeiro]

If you're working in Ember there isn't really a use for anything aside from the ember-cli, the community is putting its weight behind it and other tools will be lacking in integration. That said, I've used Webpack lately and Grunt in the past and I've really liked the way Webpack does things.