Show HN: Node-android – Run Node.js on Android
1–10 of 29 posts
Re: Show HN: Node-android – Run Node.js on Android
#2This is cool, but Termux gives you this and more.
Re: Show HN: Node-android – Run Node.js on Android
#3Serious question: what sorts of things would a person do with this?
Not throwing rocks, this is a question based in my own ignorance. I know what Node is, but I don't use it and I'm not an Android dev. Thanks!
Re: Show HN: Node-android – Run Node.js on Android
#4Very nice! I've been playing with https://github.com/janeasystems/nodejs-mobile to get the Dat project to run on Android and iOS. This might be another way to do the same thing on Android!
Re: Show HN: Node-android – Run Node.js on Android
#5This looks like a NodeJS implementation written in Java (I'm guessing from a dead-push to make Java's JS VM capable of running NodeJS APIs - and note that its compatible with Node 0.10.x - very oldish) Still would likely fill a niche where previously not possible.
Re: Show HN: Node-android – Run Node.js on Android
#6I'm probably being blind here, but why would you need to re-write node.js in Java in order to be able to run it under Android? Why couldn't this be achieved through JNI (or similar)?
Re: Show HN: Node-android – Run Node.js on Android
#7Great hack, but what does it give me that Node under Termux doesn't?
Re: Show HN: Node-android – Run Node.js on Android
#8Why link to a fork?
Re: Show HN: Node-android – Run Node.js on Android
#9"Run Node.js on Android by rewrite Node.js in Java"
It also hasn't been meaningfully updated in two years. I don't think that this is really useable.
Re: Show HN: Node-android – Run Node.js on Android
#10If the purpose is to just run JavaScript code on Android outside of a browser context, React Native and NativeScript have been doing this for a while.
If the purpose is to run JavaScript functions as background services this is somewhat implemented via Service Workers in Progressive Web Apps.
I don't think there is any way (currently) to register a JavaScript function/library as an always-on server process. I don't see why this would be unsafe or particularly undesirable unless there is something computationally intensive happening.