So there is this little petition online ADO .NET Entity Framework Vote of No Confidence. Which seems to have evoked a response from the Entity Framework team.
But I don’t care to be talked down to by the so called experts. “Warning” poor old me not to use technology that does not fit their. It seems obvious to them that all domain’s and software shops are the same, and I clearly cannot evaluate a framework.( Maybe this is true, I am on windows after all. But then what does that say about them?)
There are cases where the Entity Framework will prove most useful. While POCO can be nice, it’s not always what I am looking for. Some times I do actually need data storage. And some times persistence ignorance is not a benefit.
I would like to thank Kathleen and Julie for their contrarily posts to the petition.
Kathleen Dollard: Entity Framework Petition
Julie Lerman: Oh that no-confidence vote on E.F.
Jimmy Nilsson*, the author of Applying Domain-Driven Design and Patterns: With Examples in C# and .NET, defines the term persistence ignorance (PI) as a property of "ordinary classes where you focus on the business problem at hand without adding stuff for infrastructure-related reasons. ... The classes should focus on the business problem at hand. Nothing else should be in the classes in the Domain Model."
Remember Me
a@href@title, b, blockquote@cite, em, i, strike, strong, sub, super, u
Disclaimer The opinions expressed herein are my own personal opinions and do not represent my employer's view in anyway.