To view parent comment, click here.
To read all comments associated with this story, please click here.
Let me sum up what they had to do to make this happen:
- Implement UI virtualization with a scrolling list
- Used IFrame partitioning to reduce DOM count
- Stopping rendering while scrolling
- Implementing what amounts to a Dispatcher queue in XAML land
Why the hell should developers need to implement this themselves to get reasonable performance out of a mobile app?
The "promise" of mobile apps was reusing existing knowledge, not having to learn to write a bunch of boilerplate that most non-braindead UI platforms do for you already.
Comparing a native stack like XAML to HTML5 is like comparing an internal combustion engine to a stack of pancakes. HTML5 is so primitive its almost offensive that people still consider it a viable app platform.




Member since:
2009-08-18
To be fair, sencha wrote the facebook app properly and it worked fine.
http://www.netmagazine.com/news/senchas-html5-remake-facebook-12246...
However write once, run anywhere unfortunately is a myth.