Why do people use linq to sql?

Question

Given the premise:

• There are competent sql programmers (correlary - writing sql queries are not an issue)
• There are competent application developers (corr

Answer 1

Existing question/answers in the same vein/spirit:

• Doesn't Linq to SQL miss the point? Aren't ORM-mappers (SubSonic, etc.) sub-optimal solutions?
• LINQ-to-SQL vs stored procedures?
• What's wrong with Linq to SQL?
• Why do I need Stored Procedures when I have LINQ to SQL
• If using LINQ to SQL is there any good reason to learn SQL queries/syntax anymore?
• https://stackoverflow.com/questions/216569/are-the-days-of-the-stored-procedure-numbered

I personally believe there's no right or wrong answer. It depends on what you're developing and how you're developing it. If you need razor-sharp performance, have an overly-complex data model, etc... skip the abstraction. If you feel the abstraction speeds up your development time, like the idea of capturing all application logic in a single codebase, etc... use it.