Hacker News Reader

Comment by Touche | Hacker News Reader

Note that you should not choose Ember if you are creating an app intended to be used on mobile, as it doesn't yet have code-splitting. This talk explains about why this is a hard requirement: https://www.youtube.com/watch?v=4bZvq3nodf4

View on HN

LinkedIn has actually done a ton of work optimizing Ember for mobile devices, and they've got code splitting (what we call lazy engines) in production already: https://twitter.com/trentmwillis/status/796748896659800064

It isn't just worse on Android it is BRUTAL on Android.

I was deeply unhappy with the 3x-5x widening iOS and Android JavaScript perf gaps through 2014 and 2015 (TL;DR Qualcomm has completely lost the plot) but in 2016, it's.. even worse.

The good news is, Ember 2.10 looks like a major speed improvement! The bad news is, Android is still 10x slower with Ember.

http://discuss.emberjs.com/t/why-is-ember-3x-5x-slower-on-an...

It would be a bit more even if Apple wasn't delivering substantial speed improvements, year after year, consistently.

You're talking about rendering performance, but I'm talking about performance issues caused by bundle size.

Actually they have a strategy for your problem by enabling server-side rendering: http://ember-fastboot.com/

That doesn't help much. Server rendering means the user can see something, but if the browser is executing a 2mb blob of JS and it takes 3 seconds to do so you get major jank.

I'm confused as to how Fastboot does not help?

I hear it's worst on Android.

Reply on news.ycombinator.com