For us the switch was mostly driven by constantly bumping into file descriptor limits and the faster SASS compiler (libsass is written in C instead of Ruby). Overall, we were able to shave 50-60% off our incremental build times.
Are you on Windows? The way indexing works on Windows screws with Broccoli, and is a known issue. Even on pretty enterprisey stuff, I usually don’t see a build time over 400ms, and over half of that is usually SASS.
@ccarterc I’d be interested in seeing the output of your build. It should show whole the culprit(s) is/are.
For our largest app, our build times went form literally 60 seconds to 2-5seconds (depending on what has changed).
Prior to ember-cli, the story for sharing components was a complex one and something very few attempted. Now head on over to emberaddons.com and you can see the door it has opened
Indexing is turned off for the entire repo. I literally have one route, one controller, one template. It’s a brand new app and I just started. Build times are 15-30 seconds. Slowest trees shows about 3 seconds for es6 modules. @jasonmit@kylecoberly
Oh yeah and builds are triggered sometimes several times after making only one change to a file. Very annoying. Grunt worked out of the box. Broccoli is broken out of the box. Seems like a bad move to gain adoption.