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 552165
To read all comments associated with this story, please click here.
reduz
Member since:
2006-02-25

Everyone and their aunt that pulled out a platform or browser hoped developers would write apps in HTML5. WebOS, Apple, Microsoft. It didn't catch on. Why should it be different for Firefox OS?

Reply Score: 5

moondevil Member since:
2005-07-08

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.

Writing native code allows for much fine grain control how the UI works without hacks, even if it may require rewrites of the UI part, while the application kernel is kept the same across OS.

Reply Parent Score: 6

lucas_maximus Member since:
2009-08-18

This rings true.

I spent 4 hours tracking down and finding a pure CSS fix for an IE7 rendering bug today, where tbh my time could have been spent elsewhere.

http://blog.jquery.com/2013/01/14/the-state-of-jquery-2013/

But to the point about cross-browser issues, it’s a complete myth that today’s modern browsers have no differences. Look through the jQuery source code and you’ll see plenty of places where it has to fix, patch, and mask issues in modern browsers; those problems didn’t end with IE8. jQuery 2.0 now has more patches and shims for Chrome, Safari, and Firefox than for Internet Explorer!


They are referring to modern IE rather those that are becoming legacy rather quickly. But the point is quite clear, the jQuery team obviously have to put a lot of resources into making sure that their library works the same across each browser.

Edited 2013-02-11 21:17 UTC

Reply Parent Score: 6

WorknMan Member since:
2005-11-13

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