The arrival of Node on Android: the first steps

The day before yesterday , the code by which Linus Mårtensson took into account small but important differences in support for Android and standard POSIX systems was adopted at Noah.js repository . Also appeared autoconfigurator that allows you to build Node for Android in two steps:

1. source ./android-configure ~ / android-ndk-r8d (the second parameter is the path to the NDK)
   
2. make -j8 (build android compatible binaries)

With this achievement, not everything is still smooth ( for example, there was a proposal to better adapt to sixty-four-bit systems). However, the news is such that you can jump for joy! Since the beginning of the direct (and not under cygwin) support for the Windows version of Node (and this was a long time ago - in 2011), not a single equally noticeable step in the direction of compatibility between Node and the new (not previously supported) operating systems has happened .

I will say straight away, however, that this novelty for me so far leaves more questions than answers.
')

• Will anyone take advantage of this new product, will it start producing and distributing Node assemblies for Android, .apk files?
  
• How will Node behave under Android?
  
  
  • Can I run the Node engine under Android and get a REPL console? (Is there any idea of ​​console applications in Android?)
    
  • Will it be possible to run javascript in the node console and watch its text output? Will it be possible to associate Node for Android with .js files in order to launch their shortcuts by poking on the desktop as applications?
    
  • Do I need to rotate the device to run Node on it?
    
  • Will the javascript launched in Node be able to act as a continuously running service in Android? (Just as scripts act through node-windows under Windows, through node-linux under Linux, through node-mac under Macs.)

One can only hope that over time the answers will become clear.