Yeah, it's true that lot of the sites still using Java hasn't been updated with the correct instructions about how to enable it in FF 24 yet - and they should fix that as soon as possible of course.
Still, it's a much easier thing for normal users to figure out than how to update Java (which they must do quite regularly to get Java to run at all).
I did a little Googling and it turns out that Java still runs in Chrome on Windows, it's just banned on OS X.
Yeah, it's true that lot of the sites still using Java hasn't been updated with the correct instructions about how to enable it in FF 24 yet - and they should fix that as soon as possible of course.
Unfortunately, the applets I work on at the moment run on embedded web servers in network-enabled devices. You can't just roll out a quick update to this software every time Mozilla or Oracle break things.
If you were deploying web servers on embedded devices without planning for easy and painless upgrades, joke's on you. That's terrible for your client's security.
Some of those clients' security involves (among other things) firewalled private networks, biometric access controls overseen by armed guards, and a requirement to provide complete systems free of charge for several months of testing and auditing before any new software roll-out is approved. There is no such thing as easy and painless upgrades in that kind of environment, and that is by design. You don't exactly want the patient records in your healthcare systems or the performance monitoring tools with access to all of the traffic on your telecoms infrastructure or the card processing systems at your bank to be accessible on the public WiFi, after all.
These are the exact opposite of the kinds of places you would expect an untested Firefox update to show up. You are being inconsistent. Is it a tightly-controlled environment or not?
The environment in which these devices exist and the environment in which the machines used to access them exist are not necessarily the same. Obviously they will be connected in some way, but it is perfectly rational to want to apply security updates to staff computers that might encounter software or data from external sources but which might also be used to access in-house systems that are tightly controlled.
Yep, banned on OS X, kind of frustrating since I need to use Java for work occasionally, and when I click on the link and it redirects after opening in Chrome I need to go back, copy and paste the link into Firefox.
Still, it's a much easier thing for normal users to figure out than how to update Java (which they must do quite regularly to get Java to run at all).
I did a little Googling and it turns out that Java still runs in Chrome on Windows, it's just banned on OS X.