Some people are already skipping ahead to using K, but the guys I'm most scared by are those who only use R.
Edit: this is also a nice read http://www.erights.org/talks/thesis/
Some of his current work is about allowing safe execution in JavaScript, see: https://github.com/FUDCo/proposal-frozen-realms/ and http://www-cs-students.stanford.edu/~ataly/Papers/sp11.pdf
https://sandstorm.io/about#advisors
Cap'n Proto is very much E's distributed programming concepts "ported" to other languages, and Mark helped me get the details right.
Interestingly, E takes a very different approach from standard distributed systems practices today. Most distributed programming today emphasizes stateless servers performing idempotent operations on a monolithic datastore. Stateful servers are considered too hard to get right. What E did is actually provide the vocabulary needed to be able to reason about stateful servers, so you could get them right. Stateful servers are able to achieve massively better performance, especially in terms of latency, because they don't need to hit persistent storage for every single operation. You obviously need some way to deal with machine and network failures, but E provides that.
AmbientTalk took it a few steps further, with a concept of near and far references, future pipelining, reflection etc.
edit: Oops, E already had near/far references and promises. AmbientTalk does add more on the reflection/meta-programming side of things and features for mobile ad-hoc networks such as object discovery.
[0]: http://www.amazon.com/Coders-Work-Reflections-Craft-Programm... [1]: http://javascript.crockford.com/