> I think EF needs to expand its reach far beyond relational databases. I'm not sure I could disagree more. I don't think it's feasible to abstract away the un

> I think EF needs to expand its reach far beyond relational databases. I'm not sure I could disagree more. I don't think it's feasible to abstract away the underlying realities of different data stores. That tends to end in a mediocre API that handcuffs you from utilizing the advantages of choosing varying data stores in the first place. ORMs in general already suffer this criticism with relational data stores. Trying to make an ORM cover documents and graphs and whatever else will be worse. I also thought the Microsoft and the .Net community were moving away from stuffing everything and the kitchen sink in together.