2 ms·
The issue is not wether spidermonkey or v8 is faster than dalvik, the issue is wether the UI feels responsive or not. On a low hand device,you cant honestly sa
by camus2 13y ago
The issue is not wether spidermonkey or v8 is faster than dalvik, the issue is wether the UI feels responsive or not.
On a low hand device,you cant honestly say, an HTML5 ui on firefox os will be faster and more reponsive than an android ui coded with the android framework. Wether X javascript engine is fast or not is irrelevant. Users are not stupid, they can tell a fast and responsive ui from a clunky HTML/JS one.
Finally Javascript gives you 0 tool for manual memory management,which is central for any embedded programming. On Android and Iphone one can go down to C/C++ if necessary.
The idea of a 25$ device that would run javascript programs/uis efficiently is preposterous.
- pcwalton 13y ago> Finally Javascript gives you 0 tool for manual memory management,which is central for any embedded programming. On Android and Iphone one can go down to C/C++ if necessary. asm.js offers manual memory management, with no garbage collection. You can compile C and C++ and it will run essentially natively, modulo the sandboxed safety checks.