- Click to share on Twitter (Opens in new window)
- Click to share on Facebook (Opens in new window)
- Click to share on LinkedIn (Opens in new window)
- Click to share on Pinterest (Opens in new window)
- Click to share on Pocket (Opens in new window)
- Click to share on Reddit (Opens in new window)
- Click to email a link to a friend (Opens in new window)
3 thoughts on “Why mobile web apps are slow”
Musti C. Boullra liked this on Facebook.
Apart from JS itself (you know how much I ‘love’ Java based technologies), the article is wrong at some point. It talks only about the performance of the ARM processors. I’ve worked for ARM7 and ARM9 families, they are RISC based and beleive me performance is not a problem for them. What the article misses is memory. That’s the real bottleneck. Mobile phones use NAND/NOR based memories (Flash, Disk On Chip, …). These types of memories are typically slow. If the Java machine is executed straight from NAND (as I guess) then that might be the primary bottleneck. Also, the duty NAND/NOR block reading that is necessary in order to refresh the content of the memory every few miliseconds makes mobile phone memory a root cause for any benchmarking.
I think there’s confusion between JS and Java … And JS interpreter/JIT is definitely sitting in RAM.