Did you forget Google created Dart because Javascript is a stupid mess? Google has at least 2 languages (Dart/Go) to try on before they'd even think about that turd that is javascript. And the list goes on GWT .... Google is definetly a Java shop,doing everything not to code in javascript.
I'm also of the opinion that Google will not replace Java-based Android with nodejs-based Android.
On the other hand, I think it's worth pointing out that a lot of JavaScript development does happen at Google, albeit within the confines of the Closure compiler. Some kind of nodejs project somewhere at Google would not be out of the question. It's a big company. https://www.npmjs.org/package/closurecompiler
my point is given the success of all these javascript only mobile plateforms, it's not going to happen.If one wants to develop js apps,the web is here and free.That's why these weboses make little sense.
Google invest plenty of resources in JavaScript as well - they're active in helping define ECMAScript 6, they created V8 and Angular.js, and they employ a bunch of the world's most talented JavaScript programmers.
I really don't think google will consider that seriously for the low level. The point of dalvik is to provide a consistent low level platform for arbitrary phone manufacturers to support, which is something the jvm is explicity designed for (in a more abstract manner). Node has an interesting, simple, and effective approach to concurrency, but if I am interpreting your comment correctly I do not think node is the proper choice for a phone platform. Don't mistake an ease of abstraction in one realm for an ease of abstraction in another (specifically abstractions suited towards phone apps versus concurrent processing).
Did you forget Google created Dart because Javascript is a stupid mess? Google has at least 2 languages (Dart/Go) to try on before they'd even think about that turd that is javascript. And the list goes on GWT .... Google is definetly a Java shop,doing everything not to code in javascript.