. NET language selection

. NET language selection

Import read: the. NET language to use when each organization is migrated to. NET. Microsoft provides four languages: C #, VB. NET, manageable C ++ and JScript. This article briefly discusses our views on these languages and what languages will be used.

--------------------------------------------------------------------------------

Translated by 51dotnet.com)

Source: http://www.dotnetdan.com/articles/misc/LanguageChoice.htm

Which. NET language will be used for migration of each organization to. NET. Microsoft provides four languages: C #, VB. NET, manageable C ++ and JScript. This article briefly discusses our views on these languages and what languages will be used.

In short, we believe that C # will occupy a major market share; JScript is not competitive; C ++ will be ignored, and VB. NET shows insufficient preparation for the market.

Loser

JScript

We hope that JScript will end its mission on the basis of few users. At present, there is little information about this and there is little JScript In the. NET forum. It is no longer mainstream. Don't invest money in this technology. It is wise to give up on it.

Manageable C ++

C ++, even though its new manageable form will gradually be ignored. As more and more developers tend to use languages with clear syntax, such as JScript, Java, VB. NET, and C #, the circle of C ++ is getting smaller and smaller. Another problem facing C ++ is that it cannot be used as a teaching language. Even so, experienced C ++ developers will continue to use its capabilities, templates, and multi-code inheritance and final determination. Other people can easily cope with the problem.

Winners

Specifically, it should be the winner. Because we believe that C # is the only real winner. VB. NET is not yet supported.

C # has considerable advantages

Most professional software developers, even if independently developing the Microsoft platform, will now adopt some Java language forms.

Java is more advantageous than C ++ and VB6. He has gone through many syntax features in C ++ without reducing its functions at all (it is very easy for C ++ developers to turn to Java ). It is superior to VB6.

Java occupies the highest position among most mainstream productive languages with its clear object-oriented syntax structure and huge class libraries. For this reason, many C ++ and VB developers who are good at object-oriented technology begin to transfer to Java.

C # provides a basis for those who originally did not support Microsoft to turn to Microsoft's development tools. In fact, it is the same as Java, but in their differences, C # shows its superiority. In addition, it is an ECMA standard language, so it provides potential capabilities across multiple platforms.

Seriously, C # is the smartest choice for developers who want Microsoft to have the most productive and mainstream. NET language.

VB. NET is isolated and helpless

There is still VB. NET. We still have questions about why Microsoft only makes VB. NET a more complex C. The historical background of these two languages may be the key to understanding the transformation, but we will discuss technical issues rather than market issues.

Undoubtedly, VB. NET has grown to a new stage. It has now become a member of the rapidly growing object-oriented club. But who cares about it now? Maybe a group of people dissatisfied with it and non-object-oriented programmers, but they will immediately get it. With the emergence of C #, VB. NET seems to be an outdated product, rather than an improvement.

The DecHand code generator can generate code in VB. NET or C. If you select the VB. NET option, you will get a file which implements the same function as C #, but is about 33% larger than the file generated by C. When someone reads code written in VB. NET, lengthy statements may cause a lot of trouble. When we combine this with the aforementioned reasons, we can only expect experienced object-oriented developers to prefer C # over VB. NET.

So what kind of market will we lose VB. NET? The current market has made software companies only use VB as development tools, and has created a large number of VB enthusiasts. Unfortunately, to be honest, VB. NET is not developed for these people.

Port from VB6

The workroom that only uses VB for programming may be expected to be updated from VB6 to VB. NET, and can be as easy as the existing VB upgrade. Unfortunately, they may be severely attacked. Although there is already a tool that can automatically complete the operation process, upgrading to VB. NET will still be a lot of tiring people.

As we mentioned above, VB. NET is an object-oriented language, while VB6 is not. The problem is that if you don't think about it in an object-oriented way, and many organizations do the same, you won't be able to experience the pleasure of VB. NET conversion. Because it is not just a structure, but an example of transformation, and this transformation is very expensive. Many organizations may feel that if they want to change their way of thinking, they are better off changing their language. If VB. NET is quickly eliminated, nothing can be surprised.

Fans who used to be brilliant and lonely

The final market segmentation has created fans. For them, VB6 is an alternative language. It provides simple and powerful tools to build simple applications, including GUIs.

VB. NET is not that simple. As we have said before, it is a powerful object-oriented language. But for average fans, they don't want to or need to understand '-isms' and abstract transactions in the Object-Oriented field. They just want to complete a task as quickly as possible, ignoring the details that some of our professionals require.

For this reason, these VB fans may not continue to use VB6 soon, or they will not report too much hope for it.

The future of VB. NET

The preceding annotations are only a small part of the publicly published. net beta information. When we see the final. NET products are still quite a long time away. Microsoft will use some of them to produce hidden VB.. NET complex Visual Studio. NET features. We have to wait. We can't do anything about this. We can only believe that they can do it. For the sake of development, let us give Microsoft a traditional love, so that they will work harder.

Run Time

If you see that the difference is far from what you think, you may ask "what is the performance ?", When you decide which language to use to quickly complete a product, this is what everyone naturally wants to ask.

No doubt. NET completely ruled out those standards.

To understand why the. NET language runs as fast (or slow), let's take a look at the Compilation Program, or the Compilation Program in exactly two stages.

The first phase occurs when you press Ctrl-Shift-B on Visual Studio. At this point, execute a compilation. Your Language compiler is creating an intermediate language (IL ). The second phase occurs when you run the application. The second stage is sometimes seen as JIT compilation (we may find it strange, but we cannot explain it ). It uses IL and generates local code for special CPU usage.

Microsoft is not optimistic about the code generated by the first-stage compiled IL. Instead, they began to expand all their capabilities to optimize the second stage of IL-local code compilation. They do this to make the language unknown. All. NET languages have the same running time.

Support for debugging and compilers

Visual Studio. NET provides the same complex debugging and compilation tool for all languages. When you perform Managed C ++ decoding, you will not see more details, for example, compared with other languages. You can reach the desired depth. Similarly, the automatic completion method applies to other languages.

Summary

If you want to find a safer solution, use C #. We are sure that VB. NET is so powerful now, and C # is even more so. You will not regret it because we have clearly described its production performance to you.