Mozilla Developers Testing Mobile OS 109
MojoKid writes "Mozilla has been experimenting with an interesting idea called Boot 2 Gecko. Essentially, B2G (as it's called) is a mobile operating system based on the Web, as opposed to what the project's wiki calls 'proprietary, single-vendor stacks.' Mozilla has something here. Open Web technologies provide an intriguing platform for lots of things, mobile and otherwise. The B2G project is still pretty new, but according to the project roadmap, testing has already begun and will continue through the rest of 2011. Messaging, telephony, and battery management aspects of the OS are underway, and contacts, screen/power management, and settings are scheduled. A product demo is scheduled for sometime in the first quarter of 2012."
Re:Memory footprint should be first priority (Score:5, Interesting)
Right now, b2g uses considerably less memory than Android. The difference is about 200mb on the phone I tested on.
Of course, b2g doesn't currently do much, and our memory usage will probably increase as we add more features. But we're paying close attention.
WebOS All Over Again? (Score:1, Interesting)
What advantages does this have over WebOS? What advantages does it have over running Android with FireFox mobile as the default browser?
Re:Memory footprint should be first priority (Score:2, Interesting)
How exactly are you counting? Android in all its smartphone iterations up to Gingerbread runs just fine on phones with 192MB of RAM (less than 100MB accessible by the system at runtime!)... does B2G use roughly -100MB (negative one hundred megabytes) of RAM?
If you're just counting used RAM in a task manager type app in Android: Don't bother - Android precaches very aggressively.
Re:Memory footprint should be first priority (Score:3, Interesting)
Firefox is slower than chrome, but generally uses less memory. There were a couple versions of FF that had a memory leak problm if I recall.
See http://www.dotnetperls.com/chrome-memory [dotnetperls.com] too