Thanks for your feedback Bernie. I've just looked back at my original post in this thread and see how it's misleading (I'm going to edit it), the project has moved on a lot from then - it's no longer a tool (is now a framework) and is more focused on solving problems with performance and concurrency than making development super easy.
One of the big things it offers is the ability for you to develop chatty service interfaces (good for flexibility, bad for performance) which can be consumed in a chunky fashion (meaning better performance). You can develop your software however you want to develop it, if you want to use my framework for all network comms you can but you are perfectly free to use anything else, e.g. WCF. If however you find you have client side methods that are making multiple calls through to the server then you simply pass these methods through my framework and it'll move the execution of those methods from the client to the server for you, meaning there's only one network transaction.
I'm actually using a version of this framework in a large system which uses WCF for comms. Methods that are calling through to the server multiple times are being passed through this framework and being passed to the server for execution. When they execute on the server WCF is still being used however rather than making remote calls everything is going through localhost which is obviously much faster.
There are also features of the framework that allow for high concurrency by splitting load across multiple servers.
All these things are covered in some detail here: https://github.com/tony-dinucci/Ovule.Nomad and also on the Wiki available via that link.
If you already know this stuff and I've missed your point please let me know.