title: Traditional sql approach VS ORM
body: <p>I am really frustrated of searching this answer that what is better
  - Traditional System.Data.SqlClient approach or using any ORM like EF or Dapper
  I have seen many comparisons through many links, some are : </p>
  
  <ol>
  <li><p><a href="http://www.dontpaniclabs.com/blog/post/2014/05/01/speed-comparison-dapper-vs-entity-framework/" rel="nofollow noreferrer">https://github.com/StackExchange/dapper-dot-net</a>
  <a href="https://i.stack.imgur.com/KWLiA.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/KWLiA.png" alt="enter image description here"></a></p></li>
  <li><p><a href="http://www.dontpaniclabs.com/blog/post/2014/05/01/speed-comparison-dapper-vs-entity-framework/" rel="nofollow noreferrer">http://www.dontpaniclabs.com/blog/post/2014/05/01/speed-comparison-dapper-vs-entity-framework/</a> </p></li>
  <li><p><a href="https://stackoverflow.com/questions/3360304/orm-vs-traditional-database-query-which-are-their-fields">ORM vs traditional database query, which are their fields?</a></p></li>
  </ol>
  
  <p>One thing that I can understand that, hand written traditional sql code is better in performance than any other approach. but it is still hitting in my mind that if we already had the best approach then why ORMs?</p>
  
  <p>Is it only because we want to reduce DataLayer code? or we dont want to manage our database and want to write everything there in our c# code (code/data first)</p>
  
  <p>Why EF was introduced, if only code management was the problem then, Why and how we are compromising with the performance and speed of query execution, even ORMs has limits.</p>
  
  <p>Please answer my question and let me know if any edit is required. </p>
  
  <p>My only concern is Speed and performance of my website.</p>
  
  <p>Thanks in advance.</p>