first, thank you for taking the time for such a detailed answer. I do appreciate it and it is a very interesting insight. "I haven't been able to discern what'

first, thank you for taking the time for such a detailed answer. I do appreciate it and it is a very interesting insight. "I haven't been able to discern what's particularly exciting about this approach. What do you think is uniquely interesting about this solution?" It remains to be seen if it's uniquely interesting. If it is uniquely interesting, it will be because of node.js's supposed ability to do well with distributed server type things. It is my general opinion that node.JS gets overused for quite a lot of things that it has no business being used for. But one thing I would use it for is the high concurrency, small payload size stuff like instant messaging and MMORPG's. Imagining a robotics scenario, you could enable a simulated version of a swarm of robots that runs in a webpage. with distributed sensors, you could integrate it with a web server set up using the same language- the sensors look just like some extra nodes in the distributed network. That could be nice. The nice thing about javascript of course is that, all though it is kind of dumb out of the box, it is expressive enough that you can build some useful abstractions- and manage the callback hell that people tend to run into with node.js coded naively. On the other hand it may well be making a fish climb a tree. Low level hardware stuff was never javascript's strength. What could be interesting though is the higher level event driven stuff which is harder to achieve with things like c/java/arduino