N David Brown, 2013-03-21 20:47 (Europe/Helsinki): > If so, is this for mobile /touch devices in particular? It seems to be > quite an ugly bolt-on for a difference of 100-500k which, considering > today's average internet connection speed, is insignificant (in my humble > opinion).
In my opinion, the problem with mobile devices is NOT the download size (downloading 1MB may take a little while with 0.2-0.5 Mbps mobile connection but browsers have progressive rendering to make this less visible) but the actual execution of the JavaScript. Even with desktop browsers interpreting and executing 1-2 MB of JavaScript code takes pretty much CPU power and very much RAM. Both of which are scarce resources for any mobile device because of battery usage. I think that if lightweight JSmol can do with very little CPU and RAM despite the size of the source code, it's suitable for mobile devices. Just make sure that the file sizes and headers are suitable for public caching and fits in the private cache of most mobile devices (namely the iOS is/was very picky about the files it will cache and re-fetching the JS files for the next page load is not an option). Note that the CPU and RAM usage MUST include the processing needed to interpret the JS, not just the part of processing that is required once the "applet" is ready and running. -- Mikko ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_mar _______________________________________________ Jmol-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jmol-users
