4 ms·
I don't understand why they decided that Firefox OS would be a good fit for low-end hardware, when they had empirical evidence of how poorly webOS performed. F
by pavlov 10y ago
I don't understand why they decided that Firefox OS would be a good fit for low-end hardware, when they had empirical evidence of how poorly webOS performed.
Firefox OS and webOS are essentially the same concept. Palm built theirs for 2009 top-end hardware, and it turned out that the hardware just wasn't quite enough to run a browser engine for the entire UI... And then Mozilla goes ahead and tries to do the same thing on low-end hardware that was worse than the Palm Pre.
What was the rationale here? I can only imagine this choice was imposed by the hardware partners they could round up. If so, it's a classic example of how engineering and business development manage to undermine each other to destroy a product.
- rrdharan 10y ago> I can only imagine this choice was imposed by the hardware partners they could round up. What do you mean? Seems like this was fundamentally Mozilla imposing their philosophy/faith in their web technology/platform on hardware partners rather than the other way around? (And I believe the article supports that interpretation).
- JohnBooty 10y agoYeah it's pretty difficult for me to conceive of a world where hardware vendors cared about OS implementation details like UI rendering strategies.
- pavlov 10y agoI meant the choice of low-end hardware. I feel like they could have been more successful in the ~$200 market where Nokia Lumia models did well for a while, but presumably the hardware partners didn't want to build those. And meanwhile engineering was set on a path that wouldn't work for $40 phones.
- JohnBooty 10y agoThis is addressed in the linked article in great depth. I don't think the poor performance of WebOS means that approach is fundamentally doomed, especially since FirefoxOS was a few years later... a few years during a period of massive year-over-year increases in mobile computing power. Long story short: relative to Android, they were bypassing the whole Java layer. Gecko (which is pretty mature + optimized) was essentially running on bare metal. Lose some performance here, gain some performance there. They felt this would offer strong performance. Now, to be honest, I literally have no idea how this played out in reality. Never even touched a FirefoxOS device. But, theoretically, there's no reason why this approach can't be pretty fast. At some point your apps need to talk to a widget-drawing layer. If implemented well there's no reason why an HTML-based approach can't be pretty darn fast, or at least fast enough not to be the limiting factor in your phone's performance.
- IshKebab 10y agoLol what? Relative to Java which is maybe 50% slower than native... they used Gecko, which is at least 100% slower than native in practice. There are huge obvious well-explored reasons why this can't be fast.
- smacktoward 10y ago> Palm built theirs for 2009 top-end hardware, and it turned out that the hardware just wasn't quite enough to run a browser engine for the entire UI I owned a first-gen Palm Pre, and this was not my experience. It had plenty of problems, but the UI was always responsive and pleasant to use. (More pleasant than I find Android today, on much beefier hardware nearly a decade later.)
- hajile 10y agoChrome (and v8) launched in 2008. When webOS came out, we were still early in the performance wars. Since then, browsers have become far faster using the same hardware. Layout engines have also gotten far faster (and added a lot of features). To make things worse than necessary, webOS used outdated versions of Qt webkit and v8. Unfortunately, it seems that nobody on the webOS team ever got permission to focus on non-feature work like speeding up performance (seriously, 2 minute startup time when you only have three devices?) The UI/UX for webOS was fantastic. I really wish FF (or really anyone) would have used that UI/UX as nothing since has come close.