Is VB. NET a dead end? (2)

Speaking of "excellence", I have read a lot of materials released by Microsoft Research. Frankly speaking, those are pretty good materials. Of course, I do not understand many of the content, but my understanding is gradually increasing. I remember that Microsoft Research Institute did not publish any materials about VB. NET.

In fact, compared with VB. NET, I see more works on F # (In addition, this is a project of Microsoft Research Institute. Microsoft's researchers also deliberately avoided VB. NET. For example, I see a group of excellent thread security component libraries that do not use locking for ultra-high performance-they are written in C.

When C # was first launched, it seems (probably) that Microsoft provided a policy to end Java to help JavaProgramStaff can easily transition to the. NET platform. This makes sense, VB. net is very similar to the typical VB language, so they can achieve easy transition ,. net already supports C ++, so the only language that is truly powerful is Java.

I always think that Microsoft uses C # To attract Java programmers to use. net, and then ignores them. On the contrary, I have seen that Microsoft has invested a lot of resources to make C # not only end Java in syntax, but also become an extremely exciting language in the feature group.

C # is no longer just competing with Java-it is also doing well in attracting VB. NET programmers.

I have never really used C # For any of the following reasons #:

• I have been able to compile what the VB. NET programmer can maintain.Code.
• VB. NET can always meet my needs.
• VB. NET can be used to write concise code samples, because its syntax is very detailed, people do not need to learn VB. NET to understand the purpose of the code.

Speaking of this, I have read a lot of C # code and know that it is excellent. I'm sure that after a few hours of application, the memory of Java (I once again talked about the lastic of "ending Java") will surge. In addition, an in-depth understanding of the C-style syntax will also affect my understanding. But now I have no motivation to use C.

For the moment, VB. net is my first choice. net Language; F # also began to win my heart; for commercial reasons, I need to study ironpython (I suspect that we need a dynamic language in the near future ).

I promise myself that I will try C # In the next small project (one day or shorter #. I don't think VB. NET will be more advanced than it is now, although it will not be discarded. As I no longer glued the libraries together and used the coding time for skill R & D and other such things, I needed a forward-looking language.

VB can be compatible with COM components written by C ++ programmers, just as VB. NET can easily embed. NET Framework (including common Windows APIs. F # is excellent, but there is still a lack of commercial support.

Ironpython (the last time I mentioned) cannot be compatible with Visual Studio, which is a key part of my book. Then, only C # is left. I'm very excited? This is not the case. I like them to use C #, but not C # itself. However, I feel that VB. NET has reached the limit.