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.
Permalink for comment 554144
To read all comments associated with this story, please click here.
Member since:

"Yeah so ludicrous that FF devs tried to do the same thing (the Electrolysis project) but backed down because it was a too big change to their codebase..

Well, considering that the RAM problem seems to be related to it, and that with a combination of good session management and load-on-demand after a restart, the issue of pages crashing the browser is alleviated, it seems silly.

Silly? Last I've heard they have revived the Electrolysis project for the FirefoxOS ;-)

Aaron Seigo reposted something on his blog the other day about how it was proving a limitation for web app developers, too.
I would take Aaron Seigo's post with a (big) grain of salt:
1) the link he posted, is broken now so there is no way to see if it is a good analysis or not.
2) the reason he posted this is because many criticised KDE's design where one malfunctionning plasma applet can bring down the whole desktop.
3) he 'forget' that Chrome can also be configured to have everything running in one process with a command line option..
I'm not advocating having each plasma applet running in its own process by default, but that would be handy to debug an issue with a Plasma applet, no?

Edited 2013-03-04 14:57 UTC

Reply Parent Score: 2