I have to take exception with one thing you said Igor:

EF, as in Entity Framework, has been involved in some of the worst applications I have ever seen coded. It does horrible things by design/default and if you do things right then you are losing some of the benefits of it which is coding speed. It also makes it difficult to tune, difficult to even find where poor queries are being generated from, writes poor query constructs in some cases, plan cache bloat, etc, etc, etc. I actually just presented a session today at the SQL Saturday in Prague titled "Know What Your Code is Doing to SQL Server" covering just a few of the issues with EF (and ORMs in general).

And hopefully you don't mean LINQ-to-SQL. I think that has been put out to pasture so probably not.