The myth and reality of C #

January 10, 2002

This week, Microsoft finally released. NET object-oriented flagship language C #
。 It is designed for Web services by Anders Hejlsberg, the designer of Turbo Pascal. Microsoft has been saying it as the best thing for more than 1.5 years, while the Java and open source groups scoff at it as just another language spoken by a wicked man.

In other words, the criticism of C # is everywhere. However, after several phone interviews, I got the help of Derek Ruths, the chief scientist and participant in the Advanced Reality Project, which is designed to enable any application to collaborate with one another. Ruths has developed his resence ar program in Java, but he is also actively exploring the C # language. His views with Gartnet analyst David Smith became the main point of this article on the myth and reality of C #.

C # is "Java-class." "This is true on the one hand, but in other ways it is not right," the statement said. Microsoft denies that C # is a "reaction" to Java and claims that it is a direct successor to C + +-though Java itself can think so. It is reported that porting Java applications to C + + is relatively easy, and that the API functions and classes they use have the same name. Like Java, C # also has the ability to recycle garbage memory, which means that unwanted memory is automatically recycled as the application runs. But there is a huge difference between the two languages: Java is platform-Independent and C # is largely suitable for Windows operating systems.

Java still holds a big advantage. Java is partly the result of improvements in C + +, a language that is difficult to master but very powerful. But Java has been there for a while, and C # has just begun. "So there are some insurmountable hurdles in Java that were left over from early design," Ruths said. C # adds some "sweetness," (ruths) to syntax--its keywords and concepts make the development process a little easier. On the other hand, he thinks the C # window model is weaker than Java swing. The overall survey shows that C # and Java have a comparable capability and ease of use after synthesizing both strengths and weaknesses.

C # will eventually give the Java programmer a surrender. Gartner's view differs from the above. Although Java still has a lot of power. Few people suspect that C + + and Visual Basic programmers will quickly move to C #-but for Java programmers, if they want to shift their positions, They have to dive into a self-contained world of all Microsoft platforms-and these platforms are not enough to penetrate the backend applications of the enterprise. Why should Java programmers abandon so many things? Of course. NET plan is a big incentive to occupy a niche in the Enterprise backend application, but the process takes time.

If you want to develop. Net WEB Services, you need to learn C #. Maybe it's a good idea. Microsoft's repeated sentence is "C # is the first component-oriented language in C + + family." "Ruths agree with this view" Generally speaking, it is easier. But. NET enables you to write a. NET component in any other language.

Another interesting point of view: Ruths that C # might go back to the path of the downloadable, client-run applications that Java applets walk through (but not in the mobile computing world, where Java is still eminence). COM components are always facing the desktop, so the idea is reasonable. One thing is for sure: C # will be a key part of the Visual Studio.NET that Bill Gates calls Microsoft's most important product. You will learn a lot about C # in the next few months.