M2M is machines talking with each other, no human intervention, with the machines acting on their own. Generally. Brass Monkey has a somewhat different model because their focus is on games where a smart phone is the game controller, and a web browser on a desktop computer is the game display. Hence M2M for them is a human operated machine (smart phone) talking to another machine (desktop game display) and even other machines where the games shared state is managed across the internet among other players.
We can get out of the world of "monkish real time operating systems" and highly specialized tools, and going to a compute environment where the distributed embedded device computer devices are built using the normal sorts of tools we as developers are more commonly accustomed to using. Such as Linux and normal languages.
There's a retargeting of the role of protocols like HTTP where originally it was meant for humans at a web browser, but is now often used as the transport protocol for a machine-machine custom protocol.
Low latency pseudo-real time systems.
Lives can be at stake. Emerson for example provides technologies that run nuclear power stations, clearly a life critical function (can you say Fukushima?). In the case of the guy from Brass Monkey, "real time" is life critical for virtual lives in the game environment.
The world of low energy computation is in ARM, and MIPS and Marvell sourced chips .. does or should the Node community focus any energy on that new fangled server architecture built on chips coming from the mobile device industry?
Node community has focused on end-user use cases. How do they get the machine-machine use cases?