It is inevitable that C # is becoming bloated)

When C #2.0 was released, we looked back at Java and thought how the language was so slow? But when C # grew to 3.0, it began to show a bloated state. Will this also bring about any chain effect? Six years ago, I was a supporter of Java. At that time, C # was still version 1.0. I often argue with my master about how Java is better than C #. So he gave me an answer: "Our com is nearly five years earlier than Java, so we are more mature. Our. net is 5 years later than Java, so it is more advanced ". Although there is a sense of "stealing and changing concepts", there is another concept-the contradiction between "maturity and advanced.
Many languages such as LISP, Haskell, and scheme can also be called "great". But why do few people learn it? Because we need to fill our brains with too many things. The reason why Java and C # can be quickly accepted is that they are simple and refreshing. But what will happen when C #3.0 is released next spring? Although you can regard WCF, WF, WCS, and WPF. net plug-ins are ignored, but LINQ is an unavoidable content because it has obvious advantages in processing data access (relational and non-relational, so even if you reject it, there will still be many others. In the end, it is likely that a project team can only engage in surface business development, because the underlying public encapsulation mechanisms are all written in LINQ, moreover, Enterprise Library, a "Sample project", is coming soon.
It can be said that C # is becoming increasingly bloated, which is an inevitable trend. the "main force" of the Net Language. With the emergence of new development architectures, the complexity of C # will increase. At the same time, it is likely that the longer the innovative features, after all, it involves a lot of content. As the "Main Force", in addition to considering the collaboration between language features, we also need to fully consider the processing efficiency.
However, the. NET platform has the advantage of CLS (Common Language Specification, public Language Specification) compared to Java that uses "one channel goes black ). I believe that Java designers are reluctant to modify the Java compiler for any technical trend that is "getting popular" but has not been tested in the market for two years ;. ,.. NET platform can be flags. "For example, spec # is an example. To avoid the impact of null on software ,. the net family gave birth to spec #. The purpose is to improve data verification, exception handling, and stack management capabilities through the non-null premise, so that developers can provide higher quality software, although C # is strongly typed, dynamic language-based development can also be developed based on this "little brother. net Language predecessors based on the same CLR environment, so the function is not inferior.
To sum up, C # bloated is inevitable, and it is likely that, like Visual C ++, the complexity of the language leads to the polarization of C # developers' technical capabilities. But at the same time, with the support of the experimental. NET language, even if new features need to be integrated, it will not start from the beginning like some languages. Based on the accumulation of experimental languages, I believe that when we look at the C # New syntaxes from msdn, We can rarely see some content marked as "[obsolete.