JS & HTML on Mobile Devices

:

javascript

JS

Holy war JS vs Native

:

,

Performance

Mobile WEBHybridPhoneGapIOS

Android

WinPhone

Blackberry

TizenFirefoxOSSmartTVSamsung

LG

Ubuntu TouchWindowsRTNodeWebkitWindows

Ubuntu

MacOS

, ?

,

:

?

http://mobile.smashingmagazine.com/2013/10/17/best-of-both-worlds-mixing-html5-native-code/

http://venturebeat.com/2013/11/20/html5-vs-native-vs-hybrid-mobile-apps-3500-developers-say-all-three-please

when you move your finger, the on-screen objects under your finger move along with it. No lag, no judder of dropped frames, just a pure illusion that you're physically manipulating an object.

Jason SnellTechHive, PCWorld, Macworld

DOM

GC

3 elements = 0.003 ms

1000 elements = 0.03 ms

10000 elements = 0.36 ms

+ JQuery = 2.46 ms

Native Web

chrome --enable-memory-info

window.performance.memory.totalJSHeapSize; // currently used heap memorywindow.performance.memory.usedJSHeapSize; // total heap memory

,

Generally speaking (in my personal experience), pooling objects is not going to improvespeed. Creating objects is typically very cheap. Rather, the purpose of object pooling is to cut down onperiodiclag caused by garbage collections.

"file loading"?