/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

← → days · ↑ ↓ browse · Enter similar · o open

Oracle announces Java browser plugin will be deprecated in JDK 9, scheduled for release March 2017

Oracle says goodbye to Java browser plugin in JDK 9  —  Oracle will finally deprecate its Java browser plugin in the next release of the Java SE Development Kit, JDK 9, which is scheduled for release in 2017.

CSO Online Liam Tung

Context & Ripple Effects

Oracle's deprecation of the Java browser plugin is less a surprise than a surrender to decisions browser makers had already made: Mozilla committed to dropping NPAPI plugin support from Firefox by the end of 2016 (keeping only Flash), and Apple moved to disable Flash, Java, Silverlight, and QuickTime by default in Safari 10. With two of the major browsers cutting off the delivery mechanism, an applet-based web was no longer viable.

The move also lands amid broader questions about Oracle's stewardship of Java itself — weeks earlier the company had silently halted development of Java Enterprise Edition, alarming the Java community, while Google had confirmed its next Android version would not implement Oracle's proprietary Java APIs.

First-order effects

  • Enterprises running internal applet-based applications lose their supported browser delivery path once JDK 9 ships in March 2017, forcing migration to standalone clients or rewritten web front ends before browser support disappears entirely.
  • Oracle formally concedes the client-side Java battle, narrowing the platform's footprint to server-side and embedded deployments where the plugin never mattered.

Second-order effects

  • Flash becomes the last NPAPI plugin standing after this deprecation — a position that proved temporary when Adobe announced it would stop updating and distributing Flash at the end of 2020, completing the plugin purge the browser vendors started.
  • Browser vendors get what they wanted without further enforcement work: with Oracle itself retiring the plugin, Safari's default blocking and Firefox's NPAPI cutoff face no meaningful resistance from remaining plugin publishers.

Third-order effects

  • If the pattern holds, the web consolidates fully around HTML5 and JavaScript for interactive content, ending the 2000s-era architecture of native-code plugins inside the browser — and leaving Java's future resting entirely on server-side adoption at a moment when Oracle's commitment to Java EE was already in doubt.

The trend: Legacy browser plugin technologies are being retired vendor-by-vendor as the industry completes its shift to HTML5-native web applications.