This sounds like a major move from Mozilla, but really it is not. In Chrome, you have to enable Java per site basis, and as long as the UI for enabling Java is good, it shouldn't be an issue. Java on client side is dying, anyway. And good riddance.