Permalink
Switch branches/tags
Find file Copy path
Fetching contributors…
Cannot retrieve contributors at this time
13 lines (11 sloc) 2.14 KB
---
layout: post
title: The Entity Framework paves the way to years of uneducating the masses
date: '2008-06-24T13:51:00.001+01:00'
tags:
modified_time: '2008-06-24T14:10:51.546+01:00'
blogger_id: tag:blogger.com,1999:blog-4015568221071268916.post-2783404911805818865
comments: true
blogger_orig_url: http://serialseb.blogspot.com/2008/06/entity-framework-paves-way-to-years-of.html
---
<p>This is in substance the bitter taste that's left in my mouth as EF v1 gets ready to be released.. I've been debating on this topic in user groups, meetings and within my clients: adopting EF as it stands would be a mistake as it introduces fundamental issues in the way we write code and in the way we design our architectures. We will spend years undoing the massacre done by introducing that technology as it stands, just like we still have to suffer DataSets today.</p> <p>That's why I signed the <a href="http://efvote.wufoo.com/forms/ado-net-entity-framework-vote-of-no-confidence/">ADO .NET Entity Framework Vote of No Confidence</a>.</p> <p>And today, it was announced that the Entity Framework team would adopt a transparent process in the same way as the ado.net data services team has. In this respect I'll have to remark that the ado.net data services team took <a href="http://blogs.msdn.com/astoriateam/archive/2008/05/20/merge-vs-replace-semantics-for-update-operations.aspx">the decisions they wanted to take</a>, even when the community <a href="http://blogs.msdn.com/astoriateam/archive/2008/05/20/merge-vs-replace-semantics-for-update-operations.aspx#8589947">advised against them</a>.</p> <p>Furthermore, the objections that were made against the Entity Framework have been around for a while and apparently didn't make it into the V1.</p> <p>I'll try and have an open and positive attitude towards this opening-up, but I'll notice that already there's a push within MS to adopt the entity framework everywhere. If you push for adoption of your v1 in the company and respond to criticism by promising to fix&#160; fundamental scenarios in v2, you're doing more damage than good, and this is why I have a trust problem vis-a-vis the Entity Framework and its design team.</p>