4 ms·
The problem again is not really javascript, it is DOM manipulation. You can have the fastest javascript engine ever,if the bottelneck is the DOM , there is litt
by camus 13y ago
The problem again is not really javascript, it is DOM manipulation. You can have the fastest javascript engine ever,if the bottelneck is the DOM , there is little you can do about it. And everybody doesnt own a quad-core mobile.
I like Titanium approach where the ui is native and the code is javascript,so you are basically using javascript with a specific API,not the DOM. I'd like to see more frameworks like this , or even , i'd like mobile os vendors to faciliate the use of their native framework with javascript, instead of having to use HTML5 in a webview for development. I believe that's what WP is doing. As much as i h*te MS , it is a good move.
- gummydude 13y agoUbuntu QML. http://www.ubuntu.com/phone/app-ecosystem http://www.ubuntu.com/phone/app-ecosystem
- ecopoesis 13y agoDo you have any proof that DOM manipulation is slow? This is a common refrain that I've never seen proof of (other then anecdotally). There are folks saying that the DOM is fast, and how the JS we use to manipulate it is slow. http://blog.korynunn.com/javascript/the-dom-isnt-slow-you-are/ http://blog.korynunn.com/javascript/the-dom-isnt-slow-you-ar...
- iknight 13y agoRan this on Android 4.1.1 in chrome and it was 913ms. Desktop was ~40ms on average.
- iknight 13y agoTo be fair, I'm not sure I would endeavor to make a mobile-only web app load 10000 elements to the DOM all at once. When I set to 2000, for instance, I can get below 200ms on Android 4.1.1 in chrome.
- coldtea 13y agoBelow 200ms? Still nowhere smooth enough to get to 60fps.