Ok, tell you right now, this abstraction is overengineered (akka). My Async.java class replaces the whole framework in 750 lines of Java: http://root.rupy.se/c

Ok, tell you right now, this abstraction is overengineered (akka). My Async.java class replaces the whole framework in 750 lines of Java: http://root.rupy.se/code http://root.rupy.se/code Erlang is not a good language because it can't share memory across threads. As for Go, it doesn't have real threads that can share memory either, you can't hot-deploy it and coding non-VM languages should only be done if you need the performance (3D engine). Don't know anything about Limbo except that it probably is crummy as hell and probably suffer from the same "no real threads" syndrome. The reason you don't need callbacks is because these language ARE "callback" languages. Just like Javascript. There are only two families of real usable programming languages: native: C (C++, Rust, etc.) and VM: Java (C#, F#, etc.).