Is Entity Framework Overkill for Web Applications?

EF is not overkill for web apps.

I disagree with a lot of what is stated in your referenced article. I do agree devs should have decent skills with SQL BUT ORMS do a great job in getting a devs job done more quickly.

• Speed of ORMS - They are gettingbetter all the time & they allow youto call SP's or modify the queries toget max speed when necessary. There are also great profilers out there for monitoring ORM performance like EFProf.

• Slows down the coding process -Really!!! Once learned it speeds itup.

• Devs needing to know SQL - I agree. However, ORMS especially with LINQsyntax often allow devs to write morecomplex SQL than they would have ontheir own.

• Devs write efficient queries already - REALLLYYYY!!!! Just ask the DBA his/her thoughts! I happen to think I do but so does everyone else. See the problem. :-)

• Code Bloat - Have to disagree, especially with ones that have LINQ.... It often makes the code more readable and reduces the line count often.

• Forget about LINQ - This ship hassailed. LINQ Rocks!!!! Go with it orbe left behind. It's not just used in ORMS. It can be used against, arrays, objects, XML, files, twitter and the list goes on and on.... Get to know LINQ.

The article talks about some of the inspiration of the latest developments out of MS as coming from Ruby on Rails. ROR has an ORM based on Active Record in it.....

ORMS are good. They don't have to be used everywhere and everytime but they are good and should be considered.

Although this is a general answer be wary of any opinion which has these comments in:

"X tool stinks, I write in Y tool and I can do it faster than in X tool."

Or course a Latin speaker speaks better in Latin.

EF has a learning curve, but anything new does. EF is not overkill, but as per any system being written use the right technology for the right project.