title: Entity Framework 4 vs LINQ to SQL, for small or medium-size apps, working with SQL Server
body: <p>I've seen some discussion about L2S vs EF4 on Stack Overflow back in April, when VS2010 was launched, namely:</p>
  
  <p><a href="https://stackoverflow.com/questions/2701952/dump-linq-to-sql-now-that-entity-framework-4-0-has-been-released">Dump Linq-To-Sql now that Entity Framework 4.0 has been released?</a></p>
  
  <p><a href="https://stackoverflow.com/questions/2726806/is-entity-framework-worth-moving-to-for-a-new-small-app">Is Entity Framework worth moving to for a new small app?</a></p>
  
  <p>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.</p>
  
  <p>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.</p>
  
  <p>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?</p>
  
  <p>And, of course, why...</p>