Pretty much every tech writer in the universe over the past couple of days has been weighing on how Google's Chrome OS announcement will affect their little corner of the world, and I am certainly ...

Researchers who successfully exploited Chrome and Java vulnerabilities at the Pwn2Own contest released details on the zero-day exploits.

Google Chrome 42 disables NPAPI support by default, and Project Spartan lacks ActiveX support entirely. Both of these changes prevent the use of Java in either browser.

As outlined in the NPAPI Deprecation Guide, Chrome 42, which was due this month and was recently released to the stable channel, has disabled support for the Netscape Plug-in API. The reason is ...

The old Java plugin for Chrome that let you run java applets (basically simple java programs) in a web browser circa 2003 is going away, but that was basically dead anyway.

Chrome 42, released to the stable channel today, will take a big step toward pushing old browser plugins, including Java and Silverlight, off the Web.

These steps will disable Java in Internet Explorer 9, Firefox 15.0.1, Google Chrome 22, and Safari 6.0.1. If you're using an older version of these browsers, update to the latest release.

The USPTO has posted guidance from Oracle Corporation recommending the use of Firefox, Safari and Internet Explorer to access these services in the future.