Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror

Comment Once you go Native, you never go back! (Score 1) 69

As someone who switched from a browser based OS, WebOS, to iPhone 3GS, and now to Android, I can tell you I will never go back to another laggy HTML based OS. If anything, I'd like to see Android move away from its VM based apps to something like Apple's native apps. Many apps ran better on my 3GS than they do on my much more powerful S3. Mozilla is going the wrong direction on this one. Native > Java > JavaScript

The whole idea of using HTML, CCS, and JavaScript as the back end technology for a low-end smartphone is nuts. Even the best HTML rendering engines are CPU and memory hogs. CSS was never designed for and is nearly impossible to hardware accelerate, and JavaScript is notoriously difficult to optimize and even the best VMs like V8 run orders of magnitude slower then Native code, while the VM itself takes up a massive amount of memory.

I get that Mozilla wants to put Firefox on a phone. Fine, but first, focus one building a competitive browser. At the end of the day, I want a responsive fast phone, like the iPhone or Galaxy S3, not some dog slow HTML monstrosity.

Mozilla please just invest your limited resources on making a lean browser that can compete with Chrome!

Comment Re:No Google lock-in (Score 1) 114

IMHO, the best thing about this is you get a nice OS without the Google or Apple lock-in

How do these inane comments get modded up? My Samsung Galaxy S3 is using the Amazon App Store and my phone's contacts are synced to Yahoo mail. Please explain how Google has "locked me in"? And NO, my phone is not rooted.

As someone who switched from a browser based Mobile OS, WebOS, to 3GS, and then now Android, I can tell you I will never go back to another laggy HTML based OS. If anything, I'd like to see Android move away from its VM based apps to something like Apple's native apps. Many apps ran better on my 3GS than they do on my much more powerful S3. Mozilla is going the wrong direction on this one. Native > Java > JavaScript

Why doesn't Mozilla invest their limited resources on making a lean browser that can compete with Chrome instead of a laggy OS that no-one will want.

Comment Re:WebOS (Score 2) 114

How is this different in architecture from HP's WebOS?

In Principle they are the same idea, except WebOS uses the lean webkit engine to render the desktop, while Firefox OS, uses the resource hogging Geko engine.

As a former Palm Pre Plus and Firefox user, I am a poster child as to why this is a terrible idea. I switched from Firefox to the webkit based Chrome because it was the was so much leaner and faster. I also had to leave my webkit based Pre, for a NATIVE powered iPhone. And while I dearly miss WebOS's beautiful and intuitive UI, I do not miss the dog slow performance one bit.

Why doesn't Mozilla invest their limited resources on making a lean browser that can compete with Chrome?

Slashdot Top Deals

Kill Ugly Radio - Frank Zappa

Working...