Linked by Thom Holwerda on Wed 27th Feb 2013 22:42 UTC
Mozilla & Gecko clones "Firefox OS could actually be wildly successful, no matter how underwhelming the actual phones may be. And that's because - at least for now - you're not the customer; your carrier is." I'm extremely disappointed by Firefox OS so far. There's nothing wrong with the low-end hardware we've seen during MWC, but there is something wrong with low-end hardware that can't even properly run its operating system. To make matters worse, carriers are the boss here. Terrible first impression.
Thread beginning with comment 553894
To read all comments associated with this story, please click here.
Member since:

Disclaimer: I work on the Firefox OS project so I'm biased towards it.

I wanted to chime in on the first impression many had of the operating system. The phones we're demonstrating Firefox OS on are incredibly underpowered, they've got specs comparable to the lowest-end Android phones. There's a reason for it: they're intended to be launched in emerging markets at very low prices. That's part of the project's goals, to provide a wide range of people currently limited to feature phones with a smartphone-like experience with the added benefit of optimal access to the web.

Yet there's a couple of performance aspects that I'd like to underline. If you'll have the chance of trying the handsets yourself you'll notice that their performance is not bad at all, with most apps capable of a very smooth experience (55+ FPS during transitions/animation is not uncommon). More importantly it's not bad at all when compared to similar Android handsets and it's nothing short of amazing when you realize that's just HTML, CSS and JavaScript code running on slow, single-core, single-issue ARM processors.

In addition to this the OS in general tends to use significantly less memory hungry than Android for comparable tasks, that's an aspect we were very focused on.

Just to show that I'm not making this up check Andy Rubin's comment on this:

From the article:

“There are places where Android can’t go,” he said, referring to memory and other hardware requirements.

Reply Score: 4

moondevil Member since:

I doubt that Firefox OS will ever be able to run faster as my optimized C#/Java/C++ applications.

The JavaScript JIT better be a very good one.

Reply Parent Score: 2

przemo_li Member since:

Both C# and Java use JIT...

Reply Parent Score: 4

crystall Member since:

I doubt that Firefox OS will ever be able to run faster as my optimized C#/Java/C++ applications.

It depends a lot on what you're doing, for applications with a heavy computational factor it most certainly won't (though matching Java/C# is not impossible in JavaScript). For applications leveraging the runtime more it can be every bit as fast as a native application from the user perspective.

The JavaScript JIT better be a very good one.

It is improving and some of the latest optimization frameworks being introduced @Mozilla are specifically geared towards actual web apps rather than regular web pages (the IonMonkey JIT for example).

Reply Parent Score: 3

lucas_maximus Member since:

Can you do me a massive favour and communicate to the other Firefox guys that the desktop version is still a pile of shite.

The inspector tools are shit unless you use Firebug, which is third party so it probably leaks fuck loads of memory everywhere.

When are you guys going to get you are spreading yourselves too thinly.

Reply Parent Score: 2