title: Entity Framework VS LINQ to SQL VS ADO.NET with stored procedures?
body: <p>How would you rate each of them in terms of:</p>
  
  <ol>
  <li>Performance</li>
  <li>Speed of development</li>
  <li>Neat, intuitive, maintainable code</li>
  <li>Flexibility</li>
  <li>Overall</li>
  </ol>
  
  <p>I like my SQL and so have always been a die-hard fan of ADO.NET and stored procedures but I recently had a play with Linq to SQL and was blown away by how quickly I was writing out my DataAccess layer and have decided to spend some time really understanding either Linq to SQL or EF... or neither?</p>
  
  <p>I just want to check, that there isn't a great flaw in any of these technologies that would render my research time useless. E.g. performance is terrible, it's cool for simple apps but can only take you so far.</p>
  
  <p><strong>Update:</strong>
  Can you concentrate on EF VS L2S VS SPs rather than ORM VS SPs. I'm mainly interested by EF VS L2S. But am keen to have them compared against stored procs too since plain SQl is something I know a lot about.</p>