{"id":103599,"date":"2022-03-23T15:37:14","date_gmt":"2022-03-23T13:37:14","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/vypusk-java-se-18"},"modified":"2022-03-23T15:37:14","modified_gmt":"2022-03-23T13:37:14","slug":"vypusk-java-se-18","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/vypusk-java-se-18","title":{"rendered":"Java SE 18 Release","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
After six months of development, Oracle has released Java SE 18 (Java Platform, Standard Edition 18), with the OpenJDK project serving as its reference implementation. With the removal of some outdated features, Java SE 18 maintains backward compatibility with previous releases of the Java platform \u2014 most previously written Java projects will run without changes on the new version. Installable builds of Java SE 18 (JDK, JRE, and Server JRE) are prepared for Linux (x86_64, AArch64), Windows (x86_64), and macOS (x86_64, AArch64). The reference implementation of Java 18 developed under the OpenJDK project is fully open under the GPLv2 license with exceptions from GNU ClassPath, allowing dynamic linking with commercial products. <\/p>\n
Java SE 18 is categorized as a release with a standard support period, with updates being released until the next version. For a long-term support (LTS) version, Java SE 17 should be used, with updates being provided until 2029. It is worth recalling that starting with Java 10, the project transitioned to a new development process, which involves a shorter cycle for forming new releases. New functionality is now developed in a continuously updated master branch, from which branches for stabilizing new releases are created every six months. <\/p>\n
Notable features of Java 18 include: <\/p>\n
\n
By default, UTF-8 encoding is enabled. Java APIs that handle text data with respect to character encoding will now use UTF-8 by default on all platforms, regardless of system settings and the specified locale. To revert to the old behavior, which selects encoding based on the system locale, the parameter \u2018-Dfile.encoding=COMPAT\u2019 can be used.\n
The package com.sun.net.httpserver is included, which contains the jwebserver utility and a library API that implements a simple HTTP server for serving static content (CGI and servlet-like handlers are not supported). The built-in HTTP server is not optimized for workloads and does not support access control and authentication, as it is mainly aimed at use during development for prototyping, debugging, and testing projects.\n
JavaDoc now supports the \u2018@snippet\u2019 tag for embedding working examples and code snippets into the API documentation, which can be used with verification tools, syntax highlighting, and IDE integration.\n
The implementation of the API java.lang.reflect (Core Reflection), which is intended to obtain information about methods, fields, and constructors of classes, as well as to access the internal structure of classes, has been revamped. The java.lang.reflect API itself remains unchanged but is now implemented using method handles provided by the java.lang.invoke module, instead of relying on bytecode generators. This change allows for unifying the implementations of java.lang.reflect and java.lang.invoke, and simplifies their maintenance.\n
A third preliminary implementation of the Vector API has been proposed, which provides functions for vector computations that are performed using the vector instructions of x86_64 and AArch64 processors and allow for operations to be applied simultaneously to multiple values (SIMD). Unlike the auto-vectorization capabilities for scalar operations provided in the HotSpot JIT compiler, the new API gives explicit control over vectorization for parallel data processing.\n