Java/Java SE 18: What's New, Release History & EOL Status

What Is New in Java 18

What new tools and APIs does Java 18 introduce?

Java 18 adds a minimal HTTP server for prototyping and testing. The jwebserver command starts a static server, eliminating the need for external tools during development. This matters because it streamlines quick setup for serving files locally.

The Javadoc @snippet tag simplifies including example code in API documentation. It validates syntax and integrates better with IDEs than previous comment-based approaches. In practice, this makes documentation more reliable and easier to maintain.

A new SPI for hostname resolution allows pluggable strategies beyond the OS default. This is crucial for modern applications that need custom DNS or service discovery mechanisms without complex workarounds.

How does Java 18 improve pattern matching?

Pattern matching for switch is now in its second preview (JEP 420). It enhances switch expressions and statements with pattern matching capabilities, allowing more expressive and concise code. This reduces boilerplate when dealing with complex conditional logic based on types and values.

You can now use guarded patterns directly in switch labels and enjoy improved null case handling. This evolution brings us closer to a more declarative style of Java programming, similar to functional languages.

static String formatterPatternSwitch(Object obj) {
    return switch (obj) {
        case Integer i -> String.format("int %d", i);
        case Long l    -> String.format("long %d", l);
        case Double d  -> String.format("double %f", d);
        case String s  -> String.format("String %s", s);
        default        -> obj.toString();
    };
}

What core library enhancements are included?

UTF-8 is now the default charset across all implementations and platforms (JEP 400). This resolves inconsistencies where APIs would silently use the platform default charset, leading to unpredictable behavior. Your applications will now behave consistently across different environments unless explicitly overridden.

Core reflection is reimplemented using method handles (JEP 416). This reduces the maintenance cost of the java.lang.reflect.Method and Constructor classes. For most developers, this is an internal change with no visible impact, but it modernizes the platform's foundation.

What is the status of the Vector API?

The Vector API enters its third incubator phase (JEP 417). It expresses vector computations that compile to optimal hardware instructions on supported CPU architectures. This API is for advanced developers working on high-performance computing tasks like scientific simulations or machine learning.

Performance has been improved based on feedback from previous incubations. While still not a final API, it's becoming more stable and expressive for writing platform-agnostic complex vector algorithms.

What is being deprecated in Java 18?

Object finalization has been deprecated for removal (JEP 421). The finalization mechanism is inherently flawed and has been a source of performance and reliability issues for years. You should have already migrated to try-with-resources and cleaner APIs for resource management.

This deprecation finally signals the endgame for this problematic feature. Modern Java applications should use java.lang.ref.Cleaner or PhantomReference for cleanup operations instead.