Oracle is aggressively expanding AI datacenter capacity to serve demand tied to customers and partners including OpenAI, xAI, Meta, Nvidia, and AMD. The deal for OpenAI alone is set to be worth about $300 billion over five years.
"Any exposure of source code or system-level logic is significant, because it shows how controls are implemented. In AI systems, that layer is especially critical. The orchestration, prompts, and workflows effectively define how the system operates. If those are exposed, it can make it easier to identify weaknesses or manipulate outcomes."
Devnexus 2026 was held from March 4-6, 2026 at the Georgia World Congress Center in Atlanta, Georgia. Key takeaways included: it's up to Java developers to fix enterprise AI; how to survive the AI uprising; building blocks for AI applications; how to manage an AI-driven manager; and how to improve your career.
Tracy is compatible with Kotlin from version 2.0.0 and Java from version 17. Integrations can be made with SDKs from OpenAI, Anthropic, and Gemini. The library also works with common Kotlin/LLM stacks including OkHttp and Ktor clients, as well as OpenAI, Anthropic, and Gemini ones.
The development of AI is producing multiple winners and losers among programming languages. The best-known languages in datasets regularly produce better, more consistent AI-generated code. This is one of several explanations for the continued growth of Java. This is despite problems surrounding Oracle's revenue model for the programming language, which seems to be driving the popularity of Java-compatible alternatives. Python was ahead of other programming languages: as the most popular language before the AI hype, it has remained at a lofty height.
A global survey of 2,039 Java developers published today finds 63% reporting that dead and unused code adversely affects their team's productivity, with 22% describing the impact of that technical debt as being severe. Conducted by Dimensional Research on behalf of Azul, a provider of a distribution of OpenJDK, the survey also finds that more than half (56%) now deal with a Common Vulnerability and Exposure (CVE) involving Java on a daily or weekly basis.
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.