Internet based HTML5 has an intrinsic latency due to the connection with the server. Therefore the bottleneck for performance is not cpu but rather network latency., his makes much of the discussion concerning tailed suite moot, because the real issue is data delay and not code generation optimization.
Lastly performance comparisons between Java and javascript hint that portability of code is not the bottleneck: because Java is much faster than javascript while still being portable.
> Internet based HTML5 has an intrinsic latency due to the connection with the server.
For first load, sure, just like it takes time to download and install an app. But you can then access HTML5 sites again quickly if you store data locally (using IndexedDB for example).
Comments
Internet based HTML5 has an intrinsic latency due to the connection with the server. Therefore the bottleneck for performance is not cpu but rather network latency., his makes much of the discussion concerning tailed suite moot, because the real issue is data delay and not code generation optimization.
Lastly performance comparisons between Java and javascript hint that portability of code is not the bottleneck: because Java is much faster than javascript while still being portable.
> Internet based HTML5 has an intrinsic latency due to the connection with the server.
For first load, sure, just like it takes time to download and install an app. But you can then access HTML5 sites again quickly if you store data locally (using IndexedDB for example).