Comments on: One year after the Entity Framework Vote of No Confidence…

By: Martijn Boland » Entity Framework 4.0: a fresh start (with demo application)

Sun, 22 Nov 2009 21:36:46 +0000

[...] Entity Framework 1.0 pretty much sucks (compared to alternatives), but I’m glad to see that things have improved a lot in version 4.0. [...]

By: Bas

Bas — Fri, 09 Oct 2009 17:51:06 +0000

I love to be in control of my code.
EF will generate a lot of crap.
Look at Model.designer.cs it always makes me laugh:
//This code was generated by a tool.

By: KristoferA

KristoferA — Fri, 25 Sep 2009 14:54:02 +0000

martijn :Well, that’s more or less the point I’m trying to make: it’s pushed by MS so that developers are told by their management to use it. Managers don’t read about the flaws of Version 1.0.

hmm. those 'managers' would then fall under one or several of the following labels: incompetent (for not doing their due diligence, and for not listening to those who have), naïve (for taking marketing at face value -- do they also believe in laundry detergent TV commercials?), inexperienced (seen _any_ stable v1 product out of redmond? I haven't...). oh well, it will be interesting to see what EFv3 brings, I expect it to be a lot better than v1...

By: martijn

martijn — Fri, 25 Sep 2009 11:17:34 +0000

Danny Simmons :
I’m sorry that you have had frustrations with the first release of the EF. May I humbly suggest that you give the next release of the EF (the one that will ship with .net 4 and is available in beta form now) a chance before completely writing off the EF. It’s certainly not perfect, but I hope you will find some significant improvements.

From what I've seen, the next version looks a whole lot better and I'll definitively will give it a good look. That aside, my frustrations are caused by the fact that the V1 version was positioned as the default way of doing data access and that many developers would be better off with an alternative solution that is available right now.

By: martijn

martijn — Fri, 25 Sep 2009 11:11:56 +0000

KristoferA :
I don’t think you can blame Microsoft if end users make bad decisions and go with an inferior toolkit…

The flaws and shortcomings of EFv1 are well documented around the intarweb, so it should come as no surprise to anyone that it generates ‘killer’ SQL queries that can bring a db server onto its’ knees in a pool of table scans.

Devs need to learn to evaluate the tools and technologies they are going to use, and choose the appropriate tool for the task _before_ going off developing software…

Well, that's more or less the point I'm trying to make: it's pushed by MS so that developers are told by their management to use it. Managers don't read about the flaws of Version 1.0.

By: Danny Simmons

Danny Simmons — Fri, 25 Sep 2009 03:49:05 +0000

I’m sorry that you have had frustrations with the first release of the EF. May I humbly suggest that you give the next release of the EF (the one that will ship with .net 4 and is available in beta form now) a chance before completely writing off the EF. It’s certainly not perfect, but I hope you will find some significant improvements.

- Danny

By: KristoferA

KristoferA — Fri, 25 Sep 2009 01:30:52 +0000

@Eber It has a number of performance issues. If your model is bigger than northwind/adventureworks (i.e. >100 tables or so) you’ll notice a performance hit whenever it loads the ‘model artifacts’ (csdl/ssdl/msl) when you’re about to hit the db. Next, many common and simple query constructs can result in terrible SQL queries with lots of redundant joins, where clause predicates that force table scans etc.

Funny, since they already had L2S to look at, and L2S generates excellent SQL queries that are well optimized at runtime to please the db server… …however, it seems like they decided to not look at any of the smart optimizations in L2S and just did their own thing without considering what would happen db-side.

By: KristoferA

KristoferA — Fri, 25 Sep 2009 01:23:33 +0000

I don’t think you can blame Microsoft if end users make bad decisions and go with an inferior toolkit…

The flaws and shortcomings of EFv1 are well documented around the intarweb, so it should come as no surprise to anyone that it generates ‘killer’ SQL queries that can bring a db server onto its’ knees in a pool of table scans.

Devs need to learn to evaluate the tools and technologies they are going to use, and choose the appropriate tool for the task _before_ going off developing software…

JMHO

By: Eber Irigoyen

Eber Irigoyen — Thu, 24 Sep 2009 17:58:16 +0000

EF might not have tons of features, but from what I’ve read lately, performance is not one of its weaknesses, specially when compared to NHibernate, am I missing something?

By: Tweets die vermelden Martijn Boland » One year after the Entity Framework Vote of No Confidence… -- Topsy.com

Thu, 24 Sep 2009 17:53:20 +0000

[...] Deze blogartikel was vermeld op Twitter door Adam D.. Adam D. heeft gezegd: RT @ayende: One year after the Entity Framework Vote of No Confidence… http://bit.ly/Bx1wo [...]