title: Why do people use linq to sql?
body: <p>Given the premise:</p>
  
  <ul>
  <li>There are competent sql programmers
  (correlary - writing sql queries are not an issue)</li>
  <li>There are competent application developers
  (correlary - there is simple/strong/flexible architecture for handling connections and simple queries from code)</li>
  </ul>
  
  <p>Why do people use linq to sql?</p>
  
  <ul>
  <li>There is overhead added to each transaction</li>
  <li>There is strong likelihood of performance loss for moderate-complex calculations (DBs are made for processing sets and calculations and had teams of engineers working out optimization - why mess with this?)</li>
  <li>There is loss of flexibility (if you want to add another ui (non .NET app) or access method, you either have to put the queries back in the db or make a separate data access layer) </li>
  <li>There is loss of security by not having a centralized control of write/update/read on db (for example, a record has changed - if you allow applications to use linq to sql to update, then you cannot prove which application changed it or what instance of an application changed it)</li>
  </ul>
  
  <p>I keep seeing questions about linq to sql and am wondering if I'm missing something.</p>