Daniel Simmons, talks about persistence ignorance and how it will be incorporated in next version(s) of the ADO.NET Entity Framework. In a previous post, I already mentioned the lack of persistence ignorance for the business objects. He mentions that you have to sacrifice some performance when you want to isolate your business objects from persistence, wich is fine by me. I don't care about that. I believe this is a good step forward for the entity framework. It's still questionable that the first version(s) will be good enough to use with DDD approaches (also see this post from Scott Bellware), but there is hope for the future. Kudos to the ADO.NET team for their efforts to actually get down and listen to the community and incorporating the feedback into the binaries the as well.
