Entity Framework 4 vs LINQ to SQL, for small or medium-size apps, working with SQL Server

Question

I've seen some discussion about L2S vs EF4 on Stack Overflow back in April, when VS2010 was launched, namely:

Dump Linq-To-Sql now that Entity Framework 4.0 has been released?

Is Entity Framework worth moving to for a new small app?

Now, after 6 months, presumably people have had more interacting with EF4, so I'm curious of fresh opinions, especially when considering working only with SQL Server.

I've used LINQ to SQL a lot, and only played a bit with EF4. I wouldn't mind jumping in and learning more EF4, I'm not convinced though that it's worth the extra complexity, if my app is only going to talk to SQL Server.

So, if you had some experience with both, and you were to start a new small or medium-size app today, with a SQL Server back-end, which one would you choose?

And, of course, why...

Answer 1

Nhibernate. Or BLToolkit for special cases. Linq2Sql and EntityFraemwork are still generations behind.

Answer 2

The company I work for is a $2.5B to $3.0B solar manufacturing company. We're using L2S for all of our next generation manufacturing applications. It's not without its warts, but we've found it to be fast (contrary to what many think), nimble and very easy to work with. We have no regrets. It does everything we need it to do.