![]() The overall goal of modularizing JDK and JRE is to leverage performance, maintainability, and security. This is a problem akin to carrying an arsenal when you only need a gun. ![]() As a result, a program that only required a subset of services had no other option but to ship the whole JRE with the program. Until Java 9, both JRE and JDK were a monolithic artefact. The services such as libraries, garbage collection, and so forth, are part of the runtime environment. The byte code produced by the Java compiler only makes sense to the virtual machine which is a part of the JRE. JRE is the foundation of the Java Platform and JDK provides the necessary means to create a program entity that runs on that environment. OverviewĪpart from leveraging strong encapsulation, one of the primary motivations of the Java Module System is to make it modular to an extent scalable enough to deploy even in the smallest of devices. ![]() This article describes the key structural changes brought to JRE (Java Runtime Environment) and JDK due to modularization. Java 9 went through several false alarms and finally got a push on 21 st Sept 2017. Even it had a tint of modularity in JDK (Java Development Kit) releases. The idea of modularizing Java was long overdue since Java 8. Therefore, the team had to be absolutely sure about its effect on the existing system. A structural change with even a minor glitch can be catastrophic. Over a decade, Java has become a reliable platform for many business-critical applications. ![]() The enormity of its impact is not due to the complexity involved but the jitters of imbibing something into the bloodstream that were not equipped in its initial design phases. ![]() Project Jigsaw has had a ripple effect on the entire ecosystem of Java. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |