I have to say a few words for LINQ to refute the theory that "LINQ is dead ".

Cause

Recently, I 've seen comments about "LINQ is dead" and "playing with it", and even some cool people say"ProgramDevelopment will eventually return to the Local MachineCode", Do not say whether these comments are correct, and first let's take a look at your amazing comments. The following is only an excerpt:

Remark 1

I think there are quite a few people in the garden who have learned and written a seriesArticle
Ah ~~ What's the sorrow of programmers?
By their noses

Comments 2

It's silly to be playing with LINQ.

Remark 3

Once again, it proves that it is a waste of youth following Microsoft. Be careful with C #, ladies and gentlemen,
I found that program development will eventually return to the local code, instead of hosting

Comment 4

LINQ is the most failed work of Anders. It seems that the cool man is really old.
By increasing the complexity of programs by an order of magnitude, LINQ forces programmers to jump between two syntax systems, but substantially improves development efficiency.
LINQ is dead!

Remark 5

The waste of such garbage should not survive, making programmers hard to learn!
Garbage!
Fortunately, I refused to write

I have extracted only some of the above comments. In fact, I just want to talk about the following questions:

Recognize the truth

First of all, there is no saying that "LINQ is dead" or that "LINQ to SQL is dead". The remarks about "LINQ is dead" come fromCommunityThe cause is an article titled update on LINQ to SQL and LINQ to entities roadmap by the ADO. Net team.

As. net 4.0. the Entity Framework is a data access solution recommended by us for LINQ in relational scenarios. We have listened to the customer's feedback on the connection to SQL, feedback received from the Community will be integrated to continue to develop and improve the product.

As a result, the Community guessed that Microsoft would give up LINQ to SQL. Please note that ADO. the net team only said it is recommended to use ADO. NET Entity Framework, will increase investment in it, and there is no "abandon" comment, "dead" is even more difficult to talk about! Let's take a look at this step. Even if Microsoft no longer develops the LINQ to SQL statements, what does this have to do with LINQ? Only one of the many providers in the LINQ family is LINQ to SQL. Isn't there any other products, such as LINQ to object, LINQ to XML, and LINQ to entities? Moreover, as a lightweight ORM framework, the advantages of LINQ to SQL in small and medium-sized projects and rapid development are very obvious, if you have never used LINQ to SQL, don't say how junk it is!

A small investment does not mean giving up. Even if Microsoft no longer develops LINQ to SQL, the current functions of LINQ to SQL can be used in most development scenarios. In addition, with flexible scalability, you can customize some extensions to meet your development needs.

Again: Please stop the ridiculous comments about "LINQ is dead" or "LINQ to SQL is dead!

Distinguish between concepts

As a "professional developer", please give your opinion on a technology after learning about it. At least you have to know what this technology is like? For example, if someone says "LINQ to SQL is dead", then someone says, "Fortunately, I didn't use LINQ." This is another thing about LINQ. In February June, Lao Zhao wrote an article entitled "I think it is necessary to clarify several important concepts", which introduced the differences between LINQ and LINQ to SQL, but unfortunately, there are too many friends in the community who cannot correctly distinguish between LINQ and LINQ to SQL. Seeing these comments, let's mourn for Lao Zhao's article for a minute.

I would like to repeat it again: LINQ to SQL is only one of the many providers in the LINQ family. This is true. Please do not doubt it. Do not equate LINQ with LINQ to SQL, if you think that there are too many letters in LINQ to SQL, you can use l2s instead, but do not use LINQ instead.

Hide the useless theory of LINQ

"LINQ is very spam" and "LINQ". It is really sad to see this. LINQ is just a language feature, it allows us to operate data sets using the built-in query syntax when writing code, improving our development efficiency. Of course, if your data set comes from different sources, different providers will apply. Why not connect to generics, arrays, and. the built-in basic class libraries in the Net Framework are rejected together, or even the C # language is rejected, and the so-called "Local Code" is returned, is it easier and faster to directly write a binary "01101100" program than the C # language? If yes, please forgive me. I am wrong and I apologize.

I would like to repeat it again: LINQ is just a language feature. put aside the useless theory of LINQ.

Postscript

I wrote this article. I didn't really want to talk to someone, but I just saw that everyone was misunderstanding of LINQ. Even some beginners did not dare to learn or use it because they saw the paradox that "LINQ is dead. So I can't help but stand up and say a few words. If you are offended, please forgive me!

Related Articles:

Microsoft decided to discard the two frameworks