For what type of project is Entity Framework currently suited?
I was listening to a podcast recently that was discussing at length the short comings of Entity Framework (EF).

But, their opinions may need to be taken with a grain of salt (by me), as from what I could gather:

   - These were folks that were ORM experts.
   - They either made their living off of ORM tools, or their hobby
   - They were using ORM tools for large scale applications
   - They were also very concerned with the uber-tactics of ALT.NET that I'm not necessarily concerned with (YET)

My overall question is:

   - For what type of project is Entity Framework currently suited?

But here are a few sub-questions that may help you get where I'm headed with that question:

1. Is EF better than nothing? I'm tired of doing everything by hand.
2. Does it come close to "solving the same problem" as LINQ to SQL? 2a. If yes, when would one be suited over the other? * [found a thread on this question as I was going over questions with this tag][1], so nevermind *
3. Does it lend itself to simple 'quick and dirty' applications, such as when the bulk of your administrative CRUD forms?

  [1]: http://stackoverflow.com/questions/8676/entity-framework-vs-linq-to-sql

*edit*: for those that might be curious, I am mostly working on small to medium sized applications. That can guide your response, or not.
For what type of project is Entity Framework currently suited?
===

I was listening to a podcast recently that was discussing at length the short comings of Entity Framework (EF).

But, their opinions may need to be taken with a grain of salt (by me), as from what I could gather:

   - These were folks that were ORM experts.
   - They either made their living off of ORM tools, or their hobby
   - They were using ORM tools for large scale applications
   - They were also very concerned with the uber-tactics of ALT.NET that I'm not necessarily concerned with (YET)

My overall question is:

   - For what type of project is Entity Framework currently suited?

But here are a few sub-questions that may help you get where I'm headed with that question:

1. Is EF better than nothing? I'm tired of doing everything by hand.
2. Does it come close to "solving the same problem" as LINQ to SQL? 2a. If yes, when would one be suited over the other? * [found a thread on this question as I was going over questions with this tag][1], so nevermind *
3. Does it lend itself to simple 'quick and dirty' applications, such as when the bulk of your administrative CRUD forms?

  [1]: http://stackoverflow.com/questions/8676/entity-framework-vs-linq-to-sql

*edit*: for those that might be curious, I am mostly working on small to medium sized applications. That can guide your response, or not.