Hi!

1. You can get up and running with ES much quicker than Entity Framework
2. ES is not based on reflection, the Entity Framework is (ES is faster)
3. ES is much easier to customize
4. The Entity Framework is driven off of LINQ, but LINQ is not serializable (not easily and when it is - its HUGE!). ES supports LINQ, but, IMO, their (ES) API is much better to use and ES is substantially better to serialize
5. ES responds to issues from their customers like no other. Microsoft still hasn't even addressed a simple issue like binding to an enum (as far as I know a simple task liek the enum issue should have been addressed in weeks - it was years and - nada). You get rapid support here; you get a big forum with the Entity framework, where issues go to a committee and then get passed on to who knows where and before it is resolved, they change something that kicks it back to the beginning, and then a years later it is still swirling around as a problem).
6. Look up the forums with the Entity Framework for issues related to N-Tier or Distributed applications. The responses will tell you why I think you need a degree with the Entity Framework.
7. Data Provider Independence
8. Check out this atricle http://www.kindblad.com/2009/01/11/why-you-should-not-use-the-adonet-entity-framework/

ES works! ES is fast! ES supports N-Tier applications. ES supports serialiation. ES is about to go into the stratosphere when they implement the "layered" approach to customization.

Sarosh


>Hi,
>I took a quick look at this and, TBH, failed to see anything that wasn't handled by the .NET Entity Framework. Assuming that it is faster than EF what other advantages do you see?
>Regards,
>Viv
>
>>Take a look at Entityspaces (http://www.entityspaces.net) it is very fast and its like the best of Linq and entity framework combined together.
>>
>>Sarosh
>>
>>>I haven't read the whole branch, sorry if I missed the point. What I think is Linq* is 8th wonder of .Net if not the world:) In some point in time Linq2S or L2E might seem to be awkward, slow working or whatever. But it has developed and continue to develop. People said L2S was a dead solution but it is live and well. New projects exist that would make Linq based solutions lightning fast, fast enough that no VFP developers has seen before (neither .Net). That is in theory maybe but there are targets to have subsecond response times for queries against 1 billion rows (PLinq,DryadLinq).
>>>Setting perfromance aside, even for an SQL oriented guy like me, Linq is an easy and OOPish Linq to data < g >. Sometimes I use it just to get T-SQL I need in VFP (it is easier to express my intent in object query). A simple example would be, "get any products that are sold to USA customers". Doing that in T-SQL is not hard but is not very easy either. In Linq however it is simple:
>>>

>>>from p in Products where p.OrderDetails.Any( od => od.Order.Customer.Country == "USA" ) select p;
>>>

>>>or:
>>>

>>>Products.Where( p => p.OrderDetails.Any( od => od.Order.Customer.Country == "USA" ));
>>>

>>>
>>>PS: Didn't understand a bit about semi-competent item. Maybe it was referring to me:)
>>>
>>>Cetin