J2EE VS .NET: Weighing before the game
The word "weigh in" refers to the process of two punches before the boxing. In the professional boxing competition, the boxer and broker will always use the opportunity to say weight to Zhang Yang, show your strength. Use this word to describe J2EE and .NET's competition in the server market, it can be described as precise.
Java and .NET's saliva seem to be never yet, but in fact, many large companies support these two platforms. This "war" has become a market speculation to a certain extent. This is like a career boxing, and the show that is represented by the premiere of the game is sometimes more intricate than the battle itself.
We can give J2EE and .Net Next simple comments: J2EE features are more rich; .NET is easier. At the same time, both sides are in front of the other party. The differences in the two platforms are no longer as a disorder as they deliberately advocated.
IBM has developed a complete set of IDE technology, which greatly simplifies the development process of J2EE applications. IBM donated primary IDE technology to an open source Eclipse project, and more open source populations will bring greater convenience to J2EE developers. Some observers put forward that a shortcut to simplify J2EE development is to use J2EE's simpler part, try to abandon complex parts - especially EJB. Open source JBoss application server is doing this, and it seems that it works fine. In many cases, a Tomcat application server is enough to solve all the problems.
At the same time, Microsoft also claims that .NET has made great progress in "rich" direction.
For ISV, the selection of the platform is usually not determined by interest. If you need to take care of Linux and UNIX platforms, J2EE is usually their only choice. In addition, J2EE has undertaken large hosts and UNIX style, relatively loose independence between the various components, requires a certain combination process; and .NET style is more like AS / 400 and Windows NT, all things are tight. The differences in this style (or cultural) will also affect the choice of the enterprise.
It is generally believed that Visual Studio .NET provides a large number of wizards, so relatively easy to use, the development speed is also faster. But in the face of a wide range, high complexity, it seems that some power is not from the heart. The difficulty of customization of the .NET platform is also larger, Microsoft wants you to play in their limited range.
Gartner's analysis data shows that the operating system is gradually losing the dominance of the software industry. It is expected that the income of enterprise-level server software such as 2007, integrated servers, application servers, web servers, cluster software will exceed the server operating system. From this data, it is not difficult to understand why Microsoft should continue to promote .NET's "service" concept, why Sun wants to add more and more application servers in J2EE.
Therefore, J2EE and .NET are still playing with smear and continue to learn from each other. The techniques of both parties will soon (even may have already reached the steps of Dengfeng, so the differences between the two parties in technical indicators will be small to ignore. After all, both use virtual machine technology, both handle the same three types of I / O (front-end HTTP, process communication, backend database), and reason to believe that these technologies will develop to the extreme.
Thanks for the freedom and competition market, let us have "choice pain."
Please see full text:
http://www.adtmag.com/Article.asp?id=7610
Related connections:
Java development environment aims at the front-end modeling market
Windows Server 2003 listing
