After years of bad press caused by security problems associated with the component, Oracle is eliminating the Java browser plug-in in its JDK 9 release.

If initial experiments are any indication, the team working on the Java Browser Edition (now called the Java Kernel) will be straying quite a bit from what users really need. What they need is a ...

Now is the time to disable Java in your web browser, or even remove it from your system if that is practical. Why? The bad guys are hard at work trying to exploit a zero day vulnerability in the ...

Citing security and market forces as primary factors, Oracle said it will drop support for the Java browser plug-in in JDK 9.

There's an easy way to run Java in the browser now that WebAssembly is a W3C standard. In this Java and WebAssembly tutorial, we show you how to compile Java into WASM, and invoke your Java code in ...

Oracle decided to kill off the Java browser plugin at long last. After acquiring Java in 2010, the company said that the plugin will be deprecated with the release of JDK 9.

When people talk about Java being insecure, they're talking about the browser plug-in. Java apps themselves aren't inherently insecure, it's the browser plug-in that causes problems.

And last summer, a Java vulnerability was used by the Flashback malware to create the first known large-scale botnet of Macs, which numbered more than 600,000 at its peak.

I blogged earlier about how the component marketplaces for Delphi and .NET make the Java equivalent look virtually non-existent. In looking for someone or something to blame, some may point to the ...