Friday, September 3, 2010

Java Specification split second face crisis

In fact, such a crisis for Java is already not the first time that, in the late 90 century, Java nascent Buchangshijian Jiu Yudao the first crisis. At that time Microsoft has to compete with the SUN Java between the de facto standard for power, developed its own unique version of Visual J + +, and its VS series of development kits together, it also provides a proprietary extension API. This series of acts have deviated from the SUN ...

In fact, such a crisis for Java is not the first time, and in the late 90 century, that is, there is not a long time Java have just met for the first time on the crisis. At that time Microsoft has to compete with the SUN Java between the de facto standard for power, developed its own unique version of Visual J + +, and its VS series of development kits together, it also provides a proprietary extension API. 


This series of acts have deviated from the SUN for the Java specifications. The dispute led to between SUN and Microsoft mean to criticize each other, and lawsuits. Most used in 2001 to win the end of SUN, which allow Microsoft completely left the Java camp, missed from and Java. After the incident, the use of Java also established the principle that the standard SUN Java held the right, regardless of which vendors are required to comply with the standards.

The JCP was set up in the organization, to allow more manufacturers to participate in the Java specification under development. JCP organizations appear to IBM, Oracle is very large software vendors have the opportunity to participate in the development of Java, which, to get the full Java development. If it was not the struggle between Microsoft and SUN, leading Java standards division, there would be today.

The last time the crisis is over 10 years, today's new crisis emerged. History repeat itself again. A few days ago VMWare and Google issued a statement, together into the cloud computing. And Java as the preferred development language, the name of the Java Spring framework as the preferred open source development model. Look it depends on for more than 10 years of age have Java into the new force. But 51CTO also found sharp, VMWare and Google, after a series of actions, but also bring the standard Java separatist crisis.

Although Google is open source and open networks a strong supporter of standards. However, when talking about Java standards, saying that they used a less than standard pure Java route. In other words Google will not support all of the Java standard. Would only support a part of. If the Java standard metaphor tree, then, Google support may be a part of the branches, it may just be a leaf. The argument for Google, has a similar history.

In its open source Android platform, is part of the standard strategy used. In the Android platform, only supports the basic grammar and parts of Java API, and must use Android unique architectural pattern. Bigger difference is that, Android platform, the Java program only with the standard Java program source code level compatibility, compile the results do not like this lead to the greatest features of Java, which is a compilation run into empty words everywhere.

Google and VMWare in the joint statement into the cloud, the question on the Java EE specification, Google said that they will only support a subset of the specification. Perhaps in the near future, we will see an emasculated over the Java EE version. As cloud computing platforms will use the issue of what kind of virtual machine, there is no definite news. Is likely to Google Android version of the Java EE and Java SE platform, as Java only has the appearance of a Java.

Some people might question, as is the case, why the Spring of such a standard open source Java framework for compliance will also join the alliance, need to remind everyone that, Spring's founder is itself a Java EE specification of the opponents, is hated The EJB and Java EE Web Service heavyweight people. The development of Spring is to seek to change the Java EE development model.

While it is not possible to determine the number of companies intend to apply it to their Java applications to migrate to Google under the engine, but the data from the current view, Google Application Engine communities less than 5,000 registered users, and this with the millions of Java developers to that is a fairly small number.

Two events to look, make people feel strikingly similar. Difference is that Google's strategy of more gentle, and not as a complete change to Microsoft, which of Java. However, the need to recognize that, Google is a very strong business, strong enough to allow a subset of the available Java into a subset of the de facto standard. That allows the interception of a branch from a tree and trees in the same position.

Prior to this, Spring is also done similar work, its only use a subset of Java EE, but did not Google do in-depth and complete. If you Google on Android Java EE approach and a similar way, then he do not have to care about who holds the Java trademark, nor subject to any restrictions, so that when Microsoft wanted to do but did not do.

The consequences of all this is leading to split the Java specification. With the standard distance between the farther and farther, Java developers will face as C + + developers face the same problem, although using the same programming language, but between different platform is almost impossible to communicate with each other and understanding.

No comments:

Post a Comment