Embedding Trireme in Android

[darmie]

Hello, I am working on a library that would implement NodeJS for Android and iOS application development. I am already using https://github.com/TooTallNate/NodObjC for iOS, Trireme seems like a competent candidate, but I would like to know if Trireme supports android and what are the consequences (performace wise) of using it in Android runtime.

[gbrail]

I've never tried it. I know that just getting Rhino to work on Android is a decent amount of work, but a user in the Rhino community was able to make that work (you can see this in a recent Rhino issue)

mozilla/rhino#211

In theory there's no reason why Trireme would not run on Android if Rhino worked on Android, but it would take some work and testing.

And as for performance -- we know that for CPU-intensive code Rhino is much slower than V8, and for more typical "web server" types of workloads Trireme is more like 1/3 to 1/2 the performance of standard Node. But it all depends. I would imagine that a large Node app running on Trireme Android would be pretty slow, but other apps might be just fine. It'd be great to see someone get it working though!

[darmie]

Alright. Thanks Greg.

On Fri, 15 Jan 2016 20:33 Greg Brail [email protected] wrote:

I've never tried it. I know that just getting Rhino to work on Android is
a decent amount of work, but a user in the Rhino community was able to make
that work (you can see this in a recent Rhino issue)

mozilla/rhino#211 mozilla/rhino#211

In theory there's no reason why Trireme would not run on Android if Rhino
worked on Android, but it would take some work and testing.

And as for performance -- we know that for CPU-intensive code Rhino is
much slower than V8, and for more typical "web server" types of workloads
Trireme is more like 1/3 to 1/2 the performance of standard Node. But it
all depends. I would imagine that a large Node app running on Trireme
Android would be pretty slow, but other apps might be just fine. It'd be
great to see someone get it working though!

—
Reply to this email directly or view it on GitHub
#141 (comment).