Allow me to disagree and to tell you what happened last weekend:
Last Sunday I had a call from my stepfather who "couldn't run the website to order agro food" anymore. This website runs a Java applet to manage agro food orders on-line and the code isn't signed (it's a small structure).
He tried to understand what was going on with the warning before clicking "ok/yes/run". He googled the warning and unfortunately ended up installing malwares from ads running on some PC help website/forums that promised to fix "2 just found vulnerabilities": he thought that was related since the warning actually preventing him from accessing his "working-fine-yesterday" website seemed to be about security and vulnerabilities in the plug-in.
He then tried to update Java but canceled it at the end of the process because the window with the Java propaganda ("it powers 3 billions of applications, your car, your website, etc.") looked too much like the one with malwares from before and those didn't fix the problem (not being able to access his website).
When I finally could go to his house to fix it I realized what had happened.
It is definitely not user-friendly. It was working before and in his eyes Mozilla made it not working anymore.
edit: typo and grammar
Funny, but he didn't installed the Ask toolbar :). I did when uninstalling/reinstalling Java and clicking a little bit too fast :). Hopefully it's not as tedious to remove as a trojan.
It tricks people to installing it, reports your search activity (maybe other data? I can't find details, not installing it myself), and takes major, unnecessary steps to make it hard to uninstall it. Sounds like malware to me.
Most common search suggestions for Cydoor (well known adware): http://i.imgur.com/iXqJdzU.png
Most common search suggestions for Ask Toolbar: http://i.imgur.com/HziYjkZ.png
Looks pretty similar to me.
After reviewing the facts by discussing them with nknighthb it appears the warning message that prompted me to blame Mozilla for a confusing warning message was due to Oracle and their Java warning pop-up. https://dl.dropboxusercontent.com/u/202857/java.png
My apologies :], I am a little bit ashamed for not spotting it sooner.
This is honestly what makes the Firefox warnings even more damaging than they already are.
If a brave user decides to click past the "DO NOT ENTER" sign on the Firefox warning, they are immediately presented with another worrying warning, popped up by the Java plugin. What kind of fool says "yes, please go ahead and do this dangerous thing" when two separate pieces of software have already told them not to? Not most, unfortunately.
At least I can make the Java plugin warning dialog be relatively calm by signing my JARs. The Firefox one is completely beyond my control.
I'd like to know if the Firefox developers have details on exploits that bypass the Java plugin dialogs. If they do, I'd like to know as well. If they don't, that means they're duplicating a security feature that's already in the plugin... what's the good of that? It just confuses and frightens the users of valid, secure Java applets.
I agree he's not computer savy but I am not blaming Mozilla for his installing malware. I am blaming Mozilla for a confusing message about security. See https://news.ycombinator.com/item?id=6590686
You have a user who has not been trained to not install random software, is fooled by extremely common ads, and who does not have the basic judgement necessary to not flail about when presented with something they don't understand but to consult someone who will understand.
This is a recipe for the exact scenario you described, but is in no way dependent on Firefox's Java messages. Any message appearing on their screen that they don't understand can be the trigger, including scammy ads encountered by millions of people in routine daily browsing.
[1] https://dl.dropboxusercontent.com/u/1643240/outdated_java.pn...
[3] 1 & 2 taken from this thread: https://news.ycombinator.com/item?id=6590877
That's quite a stretch.
I have a user who uses frequently one specific website and for no apparent reason Firefox decides to tell him it's now dangerous to use with fearful and technological terms (vulnerabilities, plug-in, risk, etc.).
If Mozilla decides its users are dumb and should not be trusted to allow Java applet to be run then they should not warn them with techno-cryptic messages they know their users can't understand (because if Mozilla thought they could then Mozilla would know users could make the difference between a good and a bad applet and that warning wouldn't be needed).
A shorter and less scarier note would have been a better message for everyone.
How would you rephrase the warning in fewer than 8 words that would have helped your stepfather understand the problem and how to deal with it?
It's french but I doubt the translation process would made the word count explode from 14 words to this: https://dl.dropboxusercontent.com/u/202857/java.png
(and yes, it popped up on an up-to-date firefox with up-to-date java)
Maybe I got caught by the fact I had never seen that pop-up before and Firefox just seemed to have been updated the day before.
While we are on the topic: that makes a lot of clicking to get an applet running for the first time.
http://support.mozilla.org/en-US/kb/how-to-enable-java-if-it...
edit: formatting.
The appropriate training is nothing less than years of experience working with computers or being in the IT business. Why do we believe that this ought to be standard knowledge for users? It seems to me that we're placing too much burden on the user to make good judgements in the face of insufficient application and operating system trustworthiness.
We absolutely place too much burden on end-users -- one reason the iPad is such a hit -- but "don't believe everything you read on the Internet" and "ask me before you try to fix something you don't really understand" is not a heavy burden. If it were, we'd have a lot more mechanics and a lot fewer operable cars on the road.
Anyway, this is the warning my user was given : https://dl.dropboxusercontent.com/u/202857/java.png
Unmovable window, can't close firefox without first actioning something in it, one checkbox+one butotn to allow "something scary" to run (something that wasn't scary yesterday). This is what prompted my user to google the warning.
I've had multiple calls in the past week from Java users who didn't know that and just thought the page in question had stopped working. Your idea of "easily" and theirs are very different.
It's much less strict than in Chrome, where Java doesn't run at all anymore.
I've spent much of this morning testing applets in Chrome. In fact, I've got one running right now, and I just confirmed that Chrome is up-to-date. Perhaps you've misunderstood something?
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.
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.
You're not helping your case at all.
Accept responsibility for supporting your customers, and stop lashing out at others for not doing it for you.
Mozilla is taking the only responsible course to protect the vast majority of their users. It's been a long time coming, and absolutely no one should be surprised that it finally arrived. If anything, I'm surprised it took this for the first major browser to do it.
More will follow. Adapt or die.
An unfortunate comment, because some of the devices I had in mind when writing those last few posts are in fact medical equipment.
If Java-based UIs are no longer readily available to clinical staff the way they were last week, then effectively their instruments just got broken. Delays and increased suffering for patients are all but certain consequences until the IT staff have chance to fix things again.
Fortunately, the software running on equipment that could actually cause death as a direct result of failure is written to much higher standards and shouldn't depend on this kind of technology in the first place.
If the product you are building is not future proof it is your problem not Mozilla's.
Dont blame Mozilla for your poor technology choices. Applets will eventually stop working, and you'll be responsible if your product fails , not Mozilla.
Dont blame anybody else but you. You broke the medical staff instruments by choosing or maintaining a dead technology thus putting patient lives in danger. Do you think they'll sue you ? or Mozilla if there is an accident? You are responsible.
Nothing is future-proof if the people controlling the platforms move the goalposts. We have standards and value backward compatibility for a reason: it's because violating those standards and breaking that compatibility hurts. And it's going to become Mozilla's problem if they continue down this path, because Firefox will cease to be a viable browser choice for a significant proportion of their potential market.
Dont blame Mozilla for your poor technology choices. Applets will eventually stop working
I don't know why you're writing as if I personally broke these medical devices. I've never personally worked on any of those projects, I'm just familiar with them and citing them as examples of why this sort of change is damaging.
In any case, people really should get off the "Java applets is a dead technology" bandwagon. Viable replacements using HTML/CSS/JS are very recent developments, and people have been developing web-based user interfaces for all kinds of devices for decades. Of course they're not all going to throw out all that work and rewrite everything from scratch. There's nothing wrong with it, and contrary to your claim, there is no reason those applets must eventually stop working. They'll work just fine as long as browsers run Java applets, which they've been doing just fine for many years.
Obviously applets will stop working if browser makers deliberately drop support for them even though it's been available for a very long time. However, that's like saying obviously CSS3 is no use for anything because it's not all W3C standardised in stone yet so you're stupid if you use it today because it might all be different at some arbitrary point in the future that no-one can predict. You can shoot down any technology, no matter how modern and trendy, with such a generic argument, but it doesn't demonstrate anything particularly helpful to do so.
You broke the medical staff instruments by choosing or maintaining a dead technology thus putting patient lives in danger.
No, I didn't, but if the serious software I work on were medical in nature, you could literally bet your life that I wouldn't be letting either Java or Firefox anywhere near it and would be using an entirely different level of engineering practice to build it, as I do for certain projects in other fields where reliability is essential.
However, while we build the literally life-or-death systems that way, chances are the word processor, KVM, and, yes, web browser that organisations doing vital work use for day-to-day activities are not developed to the same standards. Breaking them still hurts, if only in efficiency (which can obviously still be harmful in a medical context). Unless you're claiming that all software that runs in any medical facility must be developed to the same standards as control software for high-risk, safety-critical systems, again, your argument is so generic that it doesn't really prove anything interesting.
Actually, we've been doing that for quite some time on one of the major projects I work on that uses Java applets, for exactly this reason. We usually recommend a recent version of IE, and as a general policy we don't offer any sort of guaranteed support for Firefox or Chrome. Of course we still test on those other browsers routinely and we'll help customers who have problems if we can, but no-one is getting any money back if they break later because of the kinds of changes we're talking about.
The worrying thing for Mozilla should be how many businesses are essentially telling us that they agree and they're moving or already planning to move back to IE as their corporate standard. It's certainly not always because of Java, but choices like rapid update cycles, lack of long-term support, and willingness to drop useful functionality do seem to be generating an increasing amount of hostility from institutional users.
You're probably aware that in many, if not almost all commercial EULAs, you'll find an all-caps passage like this one I just pulled out of Apple's OS X license document:
> E. YOU FURTHER ACKNOWLEDGE THAT THE APPLE SOFTWARE AND SERVICES ARE NOT INTENDED OR SUITABLE FOR USE IN SITUATIONS OR ENVIRONMENTS WHERE THE FAILURE OR TIME DELAYS OF, OR ERRORS OR INACCURACIES IN THE CONTENT, DATA OR INFORMATION PROVIDED BY, THE APPLE SOFTWARE OR SERVICES COULD LEAD TO DEATH, PERSONAL INJURY, OR SEVERE PHYSICAL OR ENVIRONMENTAL DAMAGE, INCLUDING WITHOUT LIMITATION THE OPERATION OF NUCLEAR FACILITIES, AIRCRAFT NAVIGATION OR COMMUNICATION SYSTEMS, AIR TRAFFIC CONTROL, LIFE SUPPORT OR WEAPONS SYSTEMS.
It's stated clearly and at length because absolutely no one writing general-purpose software wants to bear this responsibility. FOSS no less than commercial, but FOSS is generally a less-attractive lawsuit target.
Trying to foist this responsibility onto Mozilla is just evil. They didn't ask for it. They didn't offer their software as a solution to medical IT's woes. But you want to blame them for obvious misuse of their software causing harm to patients.
If I were to die of an aneurysm tomorrow, would it be your fault for not being a competent neurosurgeon and healing me? No. Nor should it be Mozilla's fault that it does not produce a medical device, but a piece of software someone has decided to misuse as one.
Would that be a failure of Firefox (or other browser vendors) or a failure of hospital IT staff to manage the medical devices / desktops / network effectively?
Logically, if Firefox is not going to support long term stability and compatibility -- and clearly it doesn't in the case we're discussing -- then the only possible conclusion is that Firefox can't be part of an effectively managed IT infrastructure for these kinds of organisations. That means the correct course of action for those responsible for that infrastructure is to plan to remove any dependencies on Firefox as quickly as possible and to replace it with something more stable, which presumably means IE in this context.
You need to evaluate the ESR release, and/or find a different browser entirely. IE may indeed be the best option if you only support Windows clients. Though Microsoft hasn't exactly been shy about forcing IE along more quickly of late, either.
I'm not sure who mainline Firefox is intended for any more. That's part of the problem, I think.
It seems like Mozilla are chasing Google to the exclusion of almost anything else, and the main goal for both of them seems to be ticking boxes to say they have more bleeding edge features, even though hardly any real projects can actually use most of those features because they aren't stable and portable enough yet. Meanwhile, users get interfaces that subtly shift around every few days, developers are fighting a constant battle just to stand still, and as we've been discussing, organisations can't manage large-scale deployments robustly at all any more.
If you had a Java application, you would not have a problem. If you had a web application, you would not have a problem. If you had a C or C++ application built against either native Windows APIs or a mature cross-platform toolkit, you would not have a problem.
Instead, you rely on browsers continuing to put their users at risk by automatically running code in a constantly-leaking sandbox managed by a company that doesn't give a shit.
Understand this: Java is a hole in the defenses of modern web browsers. It is behind. Way behind. And it will remain so forever. It and its owner are not up to the task of dealing with the modern web.
So yes, you're going to be fighting a constant battle so long as you insist on relying on what everybody already knew was crap in the mid-90s.
Or you could just tell your users to click the magic button.
I work with the NHS in the UK; quite a few of the medical professionals are forced to use IE6 or IE7 because the hospital IT staff are managing their medical devices / desktops / network effectively, just as you say.
When Firefox makes a decision like this, what they apparently did not seem to consider is that they are drawing a cutoff line which has serious costs to some of their users. I didn't see any discussion of this whatsoever in the issue thread.
Imagine a relatively forward-thinking hospital that has been able to allow their staff to use fairly-recent versions of Firefox (once new versions have been vetted by IT). Changes like this may force them to stop deploying new versions completely, until some time possibly a decade from now when they're finally able to replace the Java-based UI.
You can still easily run Java applets in Firefox 24 and beyond, you just need to click the red lego block in the upper left corner and allow it. [1]
It's much less strict than in Chrome (on OS X), where Java doesn't run at all anymore.
[1] https://support.mozilla.org/en-US/kb/how-to-enable-java-if-i...