Why did Andres Heilsberg designed LINQ syntax to be different than that of SQL (whereby made an overhead for the programmers to learn a whole new thing)?
Weren’t it better if it used same syntax as of SQL?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Why did Andres Heilsberg designed LINQ syntax to be different than that of SQL (whereby made an overhead for the programmers to learn a whole new thing)?
Weren’t it better if it used same syntax as of SQL?
LINQ isn’t meant to be SQL. It’s meant to be a query language which is as independent of the data source as reasonably possible. Now admittedly it has a strong SQL bias, but it’s not meant to just be embedding SQL in source code (fortunately).
Personally, I vastly prefer LINQ’s syntax to SQL’s. In particular, the ordering is much more logical in LINQ. Just by looking at the order of the query clauses, you can see the logical order in which the query is processed. You start with a data source, possibly do some filtering, ordering etc, and usually end with a projection or grouping. Compare that with SQL, where you start off saying which columns you’re interested in, not even knowing what table you’re talking about yet.
Not only is LINQ more logical in that respect, but it allows tools to work with you better – if Visual Studio knows what data you’re starting with, then when you start writing a
selectclause (for example) it can help you with IntelliSense. Additionally, it allows the translation from LINQ query expressions into “dot notation” to be relatively simple using extension methods, without the compiler having to be aware of any details of what the query will actually do.So from my point of view: no, LINQ would be a lot worse if it had slavishly followed SQL’s syntax.