[ALOY-3] eval() of DOM scripts at app startup increasing initial load time significantly
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | High |
| Status | Closed |
| Resolution | Fixed |
| Resolution Date | 2012-07-19T11:52:07.000+0000 |
| Affected Version/s | 2012 Sprint 14 |
| Fix Version/s | 2012 Sprint 14 |
| Components | Runtime |
| Labels | n/a |
| Reporter | Tony Lukasavage |
| Assignee | Tony Lukasavage |
| Created | 2012-05-14T09:48:50.000+0000 |
| Updated | 2012-07-19T11:52:07.000+0000 |
Description
Just as the ticket states, Android is less efficient when it comes to
eval() code at runtime, and for this reason, seconds are being added on the load time of an app no matter what the developer does. The only way to avoid this is going to be loading these DOM scripts as commonjs modules (or some other wrapper) so that we don't incur the overhead of the eval().
Check these commits for details: * [https://github.com/appcelerator/ZipTi/commit/6e39ebffd41983b14b08e97cb04bdd7bc4e93742](https://github.com/appcelerator/ZipTi/commit/6e39ebffd41983b14b08e97cb04bdd7bc4e93742) * [https://github.com/appcelerator/ZipTi/commit/904aa1bcc185eb01113b25a8375128fcbee9f3fd](https://github.com/appcelerator/ZipTi/commit/904aa1bcc185eb01113b25a8375128fcbee9f3fd)
Awesome!