Feedback on using ASE on Android?
Has anyone used ASE ( Android Script Development Environment ) for anything other than proof of concept applications?
What are the main limitations?
Any feedback would be great.
a source to share
Like this step, using ASE as your actual product platform will generally be a bad move if performance is critical. This is great for rapid prototyping and / or testing your understanding of how the API works. But the performance hit isn't trivial. This is the approach Google recommends:
As for those provided by the ASE interpreters, Lua and Python are cross-compiled C binaries that run in their own process. CPython is significantly more efficient than Jython (especially since Android does not currently support JIT).
As far as Android facades are concerned, the API is primarily focused on making scripts easier to write, not the performance of those scripts. However, remember that the saying "measures first, then optimizes." ASE is about rapid development.
If you have performance issues with your application, it is probably best to use the standard Android SDK (or NDK), where you have more control over the system.
a source to share
ASE, as the name suggests, is a scripting environment.
You shouldn't use it to build full-fledged applications, it should only be used for small daily use scenarios.
those. if you thought "I'll be coding for android using python", think again: as long as you can't compile it and have full access to the library, this is not a problem.
a source to share