tag:blogger.com,1999:blog-4252428322984442391.post1581176061167839412..comments2023-05-18T05:57:45.463-07:00Comments on withoutbugs.com: Should I ever use Entity Framework 4.0?Unknownnoreply@blogger.comBlogger4125tag:blogger.com,1999:blog-4252428322984442391.post-64881455906742821292012-03-06T05:19:13.870-08:002012-03-06T05:19:13.870-08:00http://stackoverflow.com/a/132713http://stackoverflow.com/a/132713Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-4252428322984442391.post-79334540146466942222011-12-29T17:50:59.175-08:002011-12-29T17:50:59.175-08:00I agree, after using EF 4.1, conclusion - it is on...I agree, after using EF 4.1, conclusion - it is only for small sized databases. Not scalable. Very resource intensive. Slow. Slow. Long learning curve. Too much abstraction (written by programmers with lots of time to waste, and no knowledge of the real business world).<br /><br />Just because someone published a theory/concept 30 years ago (EDM) does not mean it is good or it makes sense.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-4252428322984442391.post-90479655854547365252011-06-01T05:32:17.063-07:002011-06-01T05:32:17.063-07:00Thanks for your valuable feedback.
I'm sorry...Thanks for your valuable feedback. <br /><br />I'm sorry if you were looking for a "Yes/No" sort of answer.<br /><br />I believe content is clear enough for anyone to "decide" whether or not they want to use it from the available pros and cons.Chief Editorhttps://www.blogger.com/profile/17678121382231285858noreply@blogger.comtag:blogger.com,1999:blog-4252428322984442391.post-85360786741327384392011-06-01T01:24:45.291-07:002011-06-01T01:24:45.291-07:00This is a terrible post. Its dubious and self cont...This is a terrible post. Its dubious and self contradictory. If you are going to do a post atleast put some effort to conclude it. what a waste of my time.Anonymousnoreply@blogger.com