Java 8 release had never been seen from earlier versions, we can already taste some of the exciting features. But the developer Andrew C. Oliver said, however, Java language on certain characteristics or behind .Net. For example, Java 8 of the most anticipated Lambda expressions, released in 2007, .Net 3.5 already exists. In his view, .Net existing and upcoming features far better than Java 8, if Java 9 and then do some big improvements, then the Java .Net behind more than just a little bit.
About update rate
Microsoft has the ability to make faster improvements. I remember in the very early days, Microsoft is able to do the database is updated weekly API: from ODBC, RDO, ADO to OLEDB and so on. Since the emergence of .Net, Microsoft will reach an unprecedented update rate.
But so far behind Java Why? In the early days, Java development is also very fast, from Java 1.0.2 to Java 1.1, just one year, we saw Java completely changed. From Java 1.1 to Java 1.2 only a year and a half, and Java 1.2.2 only seven months (this is an important version, just use a small version number). And after 10 months, Java has a key significance of the advent of 1.3, which is the first Java garbage collection with the released version.
Java 1.4 brought us NIO and regular expressions, but after less than two years was canceled. Java 1.4.2 version brings a garbage collector for multi-core environments. Java 1.5 can be used in a production environment brought parallel and concurrent GC (garbage collection) properties, it also adds more importantly, concurrency and NIO function, but the process took more than a year's time.
In general, Java still has a good performance, Java 6 the lock to become cheaper, but in its essence and Java 1.5 is the same, or let users wait two years. Java 7 is the first version to make major changes to the underlying VM technology, but still give users a invokedynamic features - for the JVM to better connect to other languages, but between two large versions of the update spent about five years, indeed, some of this progress is too slow.
Why the slow progress of Java?
For this problem there is a simple explanation: Sun is not a superior strength of the company. Java to create the Internet boom, but at that time Sun Sparc business is for sale.
After that, the downturn in the Internet economy, Sun decided to continue to increase its investment in the hardware business. Sun create better at the ecosystem, but it can not create a product that is required by the user. Oracle is Sun's successor, good thorough destruction of the ecosystem, the final annexation / destroy the circle of peers, but also the development of high-margin products to replace peers.
Oracle has said in a terse public statement, he said: "We all know, for a variety of commercial and political reasons, this version (Java 7) spent a lot of time."
Of course, in the analysis of Java, we must also consider what the company's financial difficulties and the Sun Java System around. Sun's Java defeats the purpose of submitting standardized, it creates its own "standards" committee, namely JCP (Java Community Process). Over time, JCP open despite a certain extent, but now both the Sun or Oracle, have an absolute veto power, they can ignore the rules, do anything you want.
What hindered the JCP? Not open, but a conflict of interest. I remember participating in the EJB3 specification developed by a supplier, it used to delay progress of the specification. Why is this? These vendors need to purchase or develop a product to integrate into their application server, if the next generation of JavaEE specification has been released, then they must also launched products as soon as possible, they do not want later than the market.
Coordination of product release, for a company to have some difficult, not to mention the several companies. So, I think the biggest problem is not due to the Java JCP caused.
Abandoned or separated from something
Sun has become the past tense, and now Oracle is "the boss", then why Java version of the release cycle still take so long? The simplest explanation is --Java too. Large projects often mean that progress was slow and fraught with risk. Here we take a look at how Java will become smaller.
First, Oracle must get rid of their "beloved" client technology. Of course, there is no better alternative to Swing and JavaFX, but the use of these technologies means that you need to be tied to the Oracle platform - at least for now.
I'm not clear what the current JavaFX client or strategic significance for the Java Oracle brings is that they seem to be designed for and VB6, Flash or some 4GL (fourth generation languages) to compete. In the modern, multi-platform environment, most people would think that touch and slide operation will be cool for some, but this trend is JavaFX and do not match. Why do we need to use the Java client to hinder the development of server-side, and there may be accompanied by various risks, such as several months of Java zero-day vulnerabilities and security issues in the discussions on how to disable Java.
Today is no longer as important as the Java language and the Java platform. Cut off from the Java platform Java language, and publish according to their own schedule, it may be easier to --Oracle important part of the launch of the Java development tools are not business for Oracle, and not for the majority of Java developers used.
