Layering an OS on top of another OS guarantees that there will be a shortage of resource for the top-most OS layer, in this case Open webOS. Ironically, Android would be the faster OS in almost any scenario in this case, especially if Android 4.0 is the underlying OS here. You can't just keep opening OSes on top of OSes and expect the last one opened to be just as fast as the first one opened. Computing doesn't work that way; diminishing returns through compounding resource allocation and all that. On desktops, at least, there have been virtualization optimizations built into more modern desktop CPUs that help alleviate this to an extent, but the fact remains you're still sharing memory resources no matter what.
Originally Posted by daexpression
But if they manage to get a full-speed version of Open webOS running on a low-end device sitting atop a modern Android 4.0 AOSP install, I have to commend them because they've done something rather amazing in that case. Until then, I'll reserve my amazement for the day we actually see it. (And, really, I'd like to see it.)
Congrats, you just pointed out the market FirefoxOS, with millions of dollars in carrier backing and devices on the ready, is aiming squarely for. And Nokia. And Android. And...pretty much everyone except iOS at this point. Is there a huge market there? Of course. Is Open webOS the answer? In all likelihood, no.
Between Android and FirefoxOS (and perhaps Nokia with a line of lower-end Windows Phones), Open webOS seems like an odd fit, especially since those companies can afford to market and sell millions of their devices whereas Open webOS "Professional" is shooting for enterprise markets and Phoenix wouldn't be able to ramp up their supply chain for production to anywhere near the numbers--nor the quality assurance, given the types of phones they appear to be looking at--that their competition can.
I haven't even mentioned marketing to build awareness, packaging costs, distribution costs, technical support costs (unless you're just abandoning them post-purchase; pointing them to a forum doesn't freakin' count), quality control costs (you have to have people checking on the people in China building these units), ongoing legal costs (if you're a corporation, you'd better have lawyers!), regulatory costs, and all the little (HUGE) things people don't stop to think about that must be covered in order to be successful with a major product. This isn't something a couple of guys in a garage can do in a mass (100,000s of units+) production environment and expect to succeed at against anyone unless they have all of those bases covered and an ongoing and significant amount of funding behind them. Lots of i's to dot and t's to cross.
I'm not sure what Phoenix is thinking if this is their plan, because they're not only going to be outfunded a few thousand times over, they're going to be outgunned by devices with active application ecosystems from Day One--well before they even get all the stuff I outlined in the above paragraph straightened out.
And in the case of FirefoxOS, their system doesn't even necessarily require downloading apps in some cases thanks to the WebAPI which allows any website built as an app to be accessed as an app--with hardware-level access--through the browser. They'll still have downloadable apps (that work in any mobile version of Firefox, no less), but it certainly isn't a requirement.