Linked by Thom Holwerda on Mon 11th Feb 2013 15:22 UTC
Mozilla & Gecko clones "'But how is it going to beat Android or iOS?' That's the reaction many people have when I tell them that I am working on Firefox OS, the new mobile operating system from Mozilla. It is a logical reaction. After all, we live in times where every major software company and its mother is releasing a mobile platform, struggling to lure developers into their new proprietary environment, APIs, libraries, etc. And indeed, many of these companies barely make it or don’t make it at all. But Firefox OS will not be directly battling against other mobile platforms. Its main objective is to change the way the world develops mobile apps, and even in the unlikely event that Firefox OS itself disappears in the process, if web-apps become mainstream, it will have succeeded."
Permalink for comment 552253
To read all comments associated with this story, please click here.
Member since:

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.

Reply Parent Score: 3