How portable is this, exactly? Previously, node-webkit looked like a great contender for a universally shippable desktop UI system, but it actually falls on se

How portable is this, exactly? Previously, node-webkit looked like a great contender for a universally shippable desktop UI system, but it actually falls on several platforms due to invalid presumptions about locally available dynamically linked libraries [1]. It would be great to see an up-front document about portability promises. Is it possible to use other languages to drive the rendering via a linked API? Thrust [2] did a good start on defining an API for using the UI components from multiple languages, but it still relies on TCP sockets -- as far as I can tell, there's no way to make my application load assets from "bundle://" and redirect that to custom handler code while forbidding other network access, and the use of a local TCP socket to communicate between the UI and the main application means there's also major reason to be concerned about CSRF attacks on localhost. We should be able to build desktop UIs without these problems. Is atom-shell pushing forward on any of these issues, and if so is there any documentation on how? [1] https://github.com/rogerwang/node-webkit/wiki/The-solution-of-lacking-libudev.so.0 https://github.com/rogerwang/node-webkit/wiki/The-solution-o... [2] https://github.com/breach/thrust https://github.com/breach/thrust