The beginning of the end of Java technology

Dollar rising and falling, Trump making more and more ugly faces for twitter, making enemies with lawyers, and meanwhile, on the information technology side, Java will be paid. That's right. Everywhere (at least in the field of technology) there is talk about Oracle's novelty in licensing the JVM to run java codes based on version 11.

When Java 8 was released, there were already comments that the next Java licenses could become paid. And there were several security flaws both in Java 8 and in the successor versions that were barely released, that if you want to aim for security, Oracle recommends that the ideal is to jump and go straight to ... 11? What is the pay?

All the programmers in the company are apprehensive, everyone, there is not one that at lunch there was no talk about this, or that Java will be paid for, or that has other solutions like OpenJDK, or that will use TomEE as an alternative solution, but the reality is that everyone is afraid of the future of technology.

The fear is in all Java programmers, especially those who only know Java and nothing else; who already look for other similar languages ​​to learn, or study, and others who are very experienced, who simply believe that they may still be required by companies when many migrate from Java to alternative technologies.

It is heard among Java programmers that Google will bring the solution with Go, but, this technology is still very restricted to Google's own cloud environment, although all the project's source code is available on the internet, it is not yet a product reliable capable of being used in large companies.

It is believed, among business analysts, related to the IT area, that the novelty will make the company adhere to the license model, and all its diversity middleware, such as servers and clustered environments with Weblogic and WebSphere, but all are unanimous in saying, that, it may be for some time.

You see, Java emerged in companies, to replace the old method of building applications on the .NET platform, many companies have left this technology in favor of evolving to a technology with global adoption by developers, mainly governed by large companies, such as Oracle , a pioneer in databases for large sectors of the industry, and this size, this weight, has led large companies to adopt Java as a multi-environment, multi-server language, depending only on the JVM and middleware infrastructure.

Only, with the advent of virtualization, we pay more and more licenses than ever before, and more and more expensive. Before, it was a license for the operating system (Windows Server), but now, we see a corporate Red Hat infrastructure (with full, paid support, which is not cheap), VMWare virtualization layer (paid too), licenses for backup applications (Veritas NetBackup, as an example), middleware applications (Weblogic / WebSphere), third party applications (SAP, OpenText, etc.), in addition to paying dearly for countless teams, each with super specialists in each of the products.

The bill is too fat, and Oracle wants to come and put the icing on this cake, which is ready to fall apart.

Short term solution, will be to keep applications without updating, keeping the legacy in Java 6 and Java 7, and using as many alternatives as possible, and the medium term solution is to adhere to the licensing model for Java 11, but what about in the long run?

We believe that it is still time to study Java, to remain firm, but also to look and focus on alternatives for the future. We don't see much of Google's Go being the focus, but perhaps OpenJDK and some separate fork-based JVM may even exist in some major Oracle process; which can put large applications at risk.