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."
Thread beginning with comment 552183
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:

Because most of us old timers have had enough of writing a ton of CSS/JavaScript/HTML hacks to make sites work as requested across all required target browsers.

Write once, hack everywhere is usually my motto in web projects.

HA! Yeah, people keep touting how HTML5 is going to take over the world, and we see how well that worked for Facebook, they wrote a mobile app in HTML5 that sucked so much ass, they switched to native apps on iOS and Android. I'm not a web developer, but even some of the most BASIC web pages I've written for myself to run on phones look completely different on Android, depending on which web browser I'm using (stock, Firefox, Chrome, etc).

I think Firefox OS has identified a real problem - having to code native apps for different platforms is a pain. But I don't think HTML5 is the right solution. Not to say that there's a better one right now that I know of, but we should be in pursuit of something better, instead of just going with something that's half-assed, and hope it won't suck so much in 5-10 years.

Reply Parent Score: 4

lucas_maximus Member since:

To be fair, sencha wrote the facebook app properly and it worked fine.

However write once, run anywhere unfortunately is a myth.

Reply Parent Score: 3

Nelson 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