Anyone who knows me knows that I just LOVE being in the middle of a controversy. Well, that's a lie. I sure know how to pick'em, though, eh?

I have to deal with java and open source people (many who I am friends with, respect and admire) harassing me because I use Microsoft products.

I have to deal with C# developers (many who I am friends with, respect and admire) harassing me because I code with VB mostly.

Now I have to deal with Domain Driven Developers (many who I am friends with, respect and admire) harassing me because I have been busting my ass learning about Entity Framework and trying to share what I know because there are going to be a lot of people who will have to learn how to use it.

So now there's this no-confidence vote to ... I think just counter all of the information about what EF is and can do to vocalize where it's failings are if you have a particular programming style which is not supported in v1 (though are targetted for v2 and important to the EF team) and to take the EF team (which is part of the Data Programmability team, which is part of the SQL Server team) to task for creating a data-centric framework. However, the way the petition is laid out is to list it's failings to be sure that nobody gets "tricked" into using Entity Framework. Not to say the only problems are from the perspective of Domain developers, or nHibernate users or those who need Persistence Ignorance. I struggle with it too, but I just don't have the same needs as those that are listed in the petition.

I was happy to see that the Entity Framework team has responded very quickly. This responsiveness is new for them, and a new part of their recently announced transparent design for v2 which they adopted from the Astoria team.