Linked by Thom Holwerda on Thu 11th Oct 2012 01:44 UTC, submitted by MOS6510
Mozilla & Gecko clones "Just under a month ago I wrote a personal post about my thoughts on Firefox OS and why I think there is something 'magical' about what it stands for and the possibilities it brings to the table. This post is a follow-up that aims to cover much of the same ground but with extra detail and more of a technical focus."
Thread beginning with comment 538248
To read all comments associated with this story, please click here.
Shane
Member since:
2005-07-06

When the answer to "why?" is "because HTML5", I know that this happened because engineering was looking for a problem to match an existing solution.

HTML5 is great, and somewhat immature, tech. However, HTML5 in and of itself does not make a great phone.

It's also pointless to compare the speed at which a HTML5 app runs in Firefox OS with the speed with which the app runs in a Webkit browser on Android. How about comparing Gekko with Dalvik instead?

Also, let's stop with this "magical" business already. Steve Jobs could barely pull it off. People, we are not Steve Jobs. OK?

Reply Score: 4

RichterKuato Member since:
2010-05-14

Where do they state "because HTML5" as the reason for Firefox OS?

I think there is legitimate concern about Mozilla zealous touting of Web apps being the future of app development. I myself wonder if they can prove it's viability for low-end devices but it sounds like you're creating a strawman.

Reply Parent Score: 2

Mrokii Member since:
2011-01-04

The article states "because it's possible", which isn't much better.

As much as I like the idea of a truly open Phone-OS I am not quite convinced that it will be as open as Mozilla wants it to be, due to the other players they have to deal with.

I also can't follow the "not being locked in"-argument. For one, that depends on how the data you use is saved and how easy it is to transfer/convert it to something/somewhere else. As history has shown, Open Source is no guarantee that you can take your data with you everywhere you go. While it's possible in theory, even if the data is "open", it is usually rather difficult for the casual user to transfer their data from one software to another, because so many still use their own format or database-fields and usually there are no converters available.

And in the case of Mozilla OS, of course people will be locked in, as there will be APIs specific to the OS. And as long as they're only available on Mozilla OS, people can't use any of the apps on anything else.

Reply Parent Score: 2

Radio Member since:
2009-06-20

When the answer to "why?" is "because HTML5", I know that this happened because engineering was looking for a problem to match an existing solution.

FirefoxOS's use of HTML5 is not a solution looking for a problem, it is a solution to a known problem: HTML5 webpages/webapps are slow in iOS and Android browser. They are sub-par compared to native apps.

And I thought it would always be the case, whatever double-core A6 and 22-nm Exynos processor we would throw behind, until FirefoxOS came and proved this belief was wrong. A barebones OS with a good rendering engine on top can do the trick.

And am rather glad the Mozilla Foudation is doing it and pushing it seriously.

Reply Parent Score: 4

crystall Member since:
2007-02-06

FirefoxOS's use of HTML5 is not a solution looking for a problem, it is a solution to a known problem: HTML5 webpages/webapps are slow in iOS and Android browser. They are sub-par compared to native apps.


I'm working on the project and I must say that one of its biggest upsides is that it puts a lot of pressure on delivering top-notch performance from fairly limited hardware.

The large optimization and tuning effort required will deliver within Firefox too (the codebase is shared) and generally should raise the bar on what kind of responsiveness and performance users will expect from web pages in general.

Reply Parent Score: 5

Shane Member since:
2005-07-06

FirefoxOS's use of HTML5 is not a solution looking for a problem, it is a solution to a known problem: HTML5 webpages/webapps are slow in iOS and Android browser. They are sub-par compared to native apps.


But you see, the goal of these other mobile platforms (iOS, Android, Windows Phone, etc.) is not to enable great HTML5 apps. The goal is simply to enable great apps.

Edited 2012-10-11 12:36 UTC

Reply Parent Score: 3

dsmogor Member since:
2005-09-01

If the only result of FFOS would be sufficient and validated in a real world set of JS APIs that are standard and that Apple and Google must implement (preserving FFOS performance) then the project can be considered a success.

I see an unobvious ally to what FF guys are trying to do: Microsoft.
Having an web view engine that is order of magnitude faster that competition would prompt web devs to finally give the platform some love.

Reply Parent Score: 2

moondevil Member since:
2005-07-08

What would you expect from a blog whose owner is the author of Foundation HTML5 Canvas?

Reply Parent Score: 2