5 ms·
Last time I had to use ember (about 2 months ago), the ember-cli tool had major performance issues. I remember rebuilds after a single line of code was changed
by realharo 11y ago
Last time I had to use ember (about 2 months ago), the ember-cli tool had major performance issues. I remember rebuilds after a single line of code was changed taking almost 10 seconds. It also generated almost 10 gigabytes of temporary files over time. Plus I remember an issue with import paths not matching real filesystem paths, which was messing with my IDE (and my brain until I figured out what was going on).
It's a good tool when it works properly, but they really need to work on those rough edges a bit.
- orf 11y ago> I remember rebuilds after a single line of code was changed taking almost 10 seconds. Do you happen to be on Windows? My Ubuntu laptop compiles changes to our pretty large app in under a second, but on Windows it does take up to 10 seconds.
- realharo 11y agoYes, it was a Windows machine. I did all the "make it faster" steps, like running the recommended script that adjusts Windows Defender and search indexing configuration, but in the end it was still very slow, even on a fairly fast SSD.
- hatsix 11y agoThere are several teams at MS using ember (and ember-cli), and they've been PR'ing improvements. (Source: MS hosted the last Seattle Ember Meetup: http://www.meetup.com/Ember-js-Seattle-Meetup/events/227879633/ http://www.meetup.com/Ember-js-Seattle-Meetup/events/2278796...) What helped me the most was moving to Node 4+, which made memory management MUCH better.