#jdk-compatibility

#jdk-compatibility

After that date, Microsoft will no longer provide security patches, bug fixes, or technical support for ASP.NET Core 2.3. Users are advised to upgrade to modern ASP.NET on .NET 10.

Company CEO David Mytton said the release of v1.0 of its Arcjet JavaScript SDK makes it possible for developers to address many of the issues as applications are being developed that DevOps teams would otherwise need to address later in the software development lifecycle (SDLC). Additionally, Arcjet is beta testing a similar SDK for Python developers, who often have even less application security expertise, added Mytton.

A study from Dimensional Research shows that 92 percent of the 2,000 respondents reported being concerned about Oracle Java pricing, up from 82 percent in the same survey last year. Those stating they were very concerned about the changes leapt from 19 percent in 2025 to 29 percent this year. In 2023, Oracle changed its Java SE subscription model, shifting from a per-user or per-processor basis to per-employee.

Microsoft's .NET Framework 3.5 development platform, which dates back to November 2007, is no longer included as an optional Windows component. Microsoft has changed its deployment model to standalone installer status for future Windows versions. In a bulletin published February 5, Microsoft said that beginning with Windows 11 Insider Preview Build 27965, .NET Framework 3.5 must be obtained as a standalone installer for applications that require it on newer major versions of Windows.

We build production platforms with AI every day, and we work with teams doing the same with their own stack -Cursor, Claude Code, Copilot. The difference shows up fast. By day two, some codebases are already harder to change than they were yesterday. Others keep getting easier. The difference is never the model. It's what the code lands in. The teams we work with that hit a wall? It's always the same story.

JEP 527, Post-Quantum Hybrid Key Exchange for TLS 1.3, has been elevated from Proposed to Target to Targeted for JDK 27. This JEP proposes to enhance the implementation of RFC 8446, Transport Layer Security (TLS) Protocol Version 1.3, using the Hybrid Key Exchange in TLS 1.3 specification, currently being drafted by the Internet Engineering Task Force (IETF) in conjunction with JEP 496, Quantum-Resistant Module-Lattice-Based Key Encapsulation Mechanism, delivered in JDK 24.