As far as I can see it's a datatable based dal, so not about entities, but about tables + SQL. I.o.w.: a step back (or two). I also find it amusing that they promote linq ... on the client side. Well... that's already in .net, linq to objects. You want linq... on the serverside. RemObjects has been around for a while now, so they're not new to the game, although as far as I know, they originate in the delphi world.
Thanks Frans. A great comparision of the points that as developers we should always be at the look out for.
I am more interested in their remoting SDK specially the idea of easily "remote-enable" a multi-tier application to be deployed on multi-physical tiers...
Remoting made 'easy' always has a price: the more you abstract away through a service, the less you can change to make things the way that fits your application best. As our remoting code is pretty fast and results in very compact datablocks, the rest is really up to the developer of the application: what do you want to do on the client side vs. what do you want to do on the server side. It's not something you can flip with a switch, it requires careful design and architecture, as otherwise you run the risk of having a service which doesn't perform under the load the application is facing and you can't change it .