Why is everyone Linq To Entities Hate?

Question

I noticed that there seems to be some hostility towards Linq To Entities towards Linq To Entities, especially from Alt.Net people. I understand the resistance to drag-and-drop programming, but, in my opinion, Linq To Entities does not require this.

We are currently using Linq for SQL, and we are using a DBML document to define it (after you get more than a dozen or so tables, the constructor will be useless.)

So why not use the same approach for Linq To Entities?

Answer 1

I do not think this is hatred of the idea of ​​this as such. It’s just that people don’t like its implementation.

http://efvote.wufoo.com/forms/ado-net-entity-framework-vote-of-no-confidence/

Answer 2

In fact, as soon as you begin to delve into this, LTE is completely useless for enterprise-level infrastructures. The fact that there is very little support for inheritance (in LTS as well) makes a lot of redundant code. In addition, I will return to LTS (Linq to SQL) because it actually allows you to define mappings through attributes instead of a file. LTE only works with an external file.

Answer 3

Linq to Entity's hatred is very noteworthy. This product does not cope with any purpose more complicated than the lame demos GU uses it for its blog. EF is far from ready for prime time. Microsoft just can't get the right data in the .BLOAT world, they seem to change the data paradigm every time the wind blows. FoxPro has been around for 20 years with the same underlying data core. Given that SQL Server uses most of the VFP data technologies, MSFT can learn a little about how to manipulate data and language-oriented data from what worked.

Answer 4

I am pretty much selling Linq sites for Entities and the Entity Framework in general, but I have doubts about its current implementation. I freely admit that I did not use it in anything other than a self-educational and very small way. The level of flexibility does not seem to exist yet, but I'm sure it will. I was told by one of the MS technology evangelists (a great job title) that EF was MS's strategic choice for the future. Assuming this is so, I can only see improvements in this arena.

Answer 5

There may also be "second place hostility." MS entered the market very late with L2E, I myself became interested in ORM about three years ago or so, and MS was nowhere to be seen at the moment.

Many of us have already taken the time to learn another ORM (for example, NHibernate) and are used to a certain level and type of functionality available, and I do not see it in L2E yet.

This “second place” of hostility is not old news, to be honest, I don’t know why MS doesn’t spend more time on supporting solutions already in place, we all saw this with NAnt → MSBuild and NUnit → MsTest, this will save everyone a lot of time and strength, if they just make one of the best and most mature decisions and try to support it, and not brew them all the time.

Answer 6

I would add that implementing LTE TPT inheritance is nothing more than a crime. See my question here .

And while I'm in it, I find that many published EF experts are at least partially involved. I have yet to find any published material on EF that warns against base type queries. If I tried it on the model I have, SQL Server simply throws an exception.

Some part of your SQL statement is too deeply nested. Rewrite the query or break it down into smaller queries.

I would like to rewrite the request, but LTE freed me from this burden. Thanks (^ not)