Skip to content

Instantly share code, notes, and snippets.

@lloyd
Created October 17, 2013 16:04
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save lloyd/7027607 to your computer and use it in GitHub Desktop.
Save lloyd/7027607 to your computer and use it in GitHub Desktop.
1. Deeply want to preserve the possibility of dynamic update. App abstraction helps.
2. Lots of JavaScript will love on this module. Jwcrypto, gherkin, and more. Nice to ensure memory is fully reclaimed.
3. Security isolation - content will cause messages to be passed in. I'd like to give this module minimal permissions for defense in depth.
4. Less likelyhood of crashing system app. I hear Andreas gets a little upset when we do that.
5. Short lifetime - this thing will run infrequently for short periods of time. Why use resources all the time?
6. Parallelization - were gonna do some computation in this process. When we move to multi core mobile we get to keep it off the main thread. Even before that, nice can help keep the phone responsive.
Any of this reasoning compelling? Shall we invite fabrics to throw stones?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment