After reading some articles, I found: Maybe, J2EE and .Net did not have any argument. Most of the institutions that have been installed and used J2EE will adhere to Java. Most of the institutions using Microsoft products are more optimistic .NET instead of Java. In fact, this is not surprising. Obviously, many Builder.com members have got the same conclusion.
C # to Java: no argument
Builder.com proposes a large number of evidence description C # relative to Java superiority, and vice versa. In fact, Craig Utley has written an article with 10 reasons to prove that development agencies should use C # instead of Java or C . UTLEY puts out some reasons, including syntax, simple and supporting objects. However, although UTLEY's reason is correct, especially in the case of comparing with C and C , it is true that Builder.com's member RJLorimer finds that these ten reasons have eight simultaneously, also explain C # The superiority is not so high.
Due to the similarity of Java and C # syntax, if you have to convert from a language to another language relatively easy. Therefore, this issue may be able to comeide to just about the debate on the hot platform.
Don't abandon J2EE
Conversely, GodFrey Baker wrote an article that advocates that developers should not go to .net from Enterprise Java Beans (EJBS). Baker proposes some reasons, including devices that do not support management and use different session processing methods. In addition, a member Jeffyjones proposed questions, is this a noble argument. "I itself is a .NET developer, but I won't use Java as the Java's developer will not use .NET. There is no reason to say this!" Another member ez9926 agreed with this view. "First, why do you want to move the Java development environment that has been established to .NET? Can it provide a faster development environment? Can it provide things that Java can't do? In the next few years, we It will be seen in Java and .NET, not Java and .NET challenges. "Even some members think that the Java work platform is called. Net is a very ridiculous thing. "What is the reason for them to make such a big adjustment, move a system that exists (and running) from one platform to another? The only reason I can think of is that their technical consultants I want to add a merit to my personal resume. "SIMON 123 is written.
Future controversy
If Java's debate is just about which platform of preference, it will develop like this trend. What do you think is .NET? A member Bayard proposed C # will occupy the customer system, while Java will continue to rule the service system. "C # and .NET will replace Java, occupy the customer market. They do this make this reason, because there are very few people who use non-Windows systems. But with .NET replacement EJB seems to be a mistake, .NET is just a new thing And use ASP alternative JSP. It seems that it is not a wise choice unless you use VB programming unless you use VB programming. The future structure is destined to write a service system with Java with a C # operation application. That is, [Microsoft] Occupy the customer system, but there is still no advantage for the service system. "
Two conclusions
I think J2EE's "argument" of .NET is mainly caused by the controversy of the platform to the platform. Organizers using Java will not give up it to use .NET, and vice versa. From (chinauml.net)
