View Single Post
Posts: 237 | Thanked: 157 times | Joined on Dec 2009 @ San Diego, CA
#29
Originally Posted by Flandry View Post
I can see that some might see it that way, but it's not really the case. Adding a mandatory javascript app layer to an OS doesn't add functionality, it takes it away (less battery life/performance). You can't do anything new with it that can't be done better without it. I.e. not really a feature...

It's rather like Apple calling the no user multitasking a feature, or the nonremovable battery. Both are "features" that restrict user options.
I tend to look at it in the light that User Freedom is (in most cases) directly proportional to Developer Freedom.

It's true that 2 different browser engines are going to use more resident memory, and CPU cycles if both are in active use simultaneously. The same is true of including both GTK+ and QT4 widget libraries.

I really only think we will see a significant battery hit if developers misuse the feature, and ignore these relevant concerns, the same problems we already see with native widgets and apps.

It fits with nokia's stated vision of Maemo, the desktop experience on a mobile. How many rendering engines do you have installed on your desktop?

We're still on the cusp of such an experience being at all feasible on devices of this size. But the amount of memory nokia will be able to cram into these is only going to get bigger.
 

The Following User Says Thank You to go1dfish For This Useful Post: