3 ms·

Yes, Mozilla has been pretty clear on this. If you want more stability, you need the ESR release, and if that's not enough, you're out of luck. Mainline Firefox

Yes, Mozilla has been pretty clear on this. If you want more stability, you need the ESR release, and if that's not enough, you're out of luck. Mainline Firefox is simply not intended for use within organizations that demand the kind of stability you want. 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.

Silhouette 13y ago
Mainline Firefox is simply not intended for use within organizations that demand the kind of stability you want. 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.
- nknighthb 13y ago
  Your mistake is in conflating Java with the browser. The two are unrelated. Neither is really built with the other in mind, their development is not integrated or synchronized in any way, and the paradigms are just generally incompatible. And now, one poses a clear and present danger to the security of the other. 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.

Silhouette 13y ago

Mainline Firefox is simply not intended for use within organizations that demand the kind of stability you want. 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.

nknighthb 13y ago
Your mistake is in conflating Java with the browser. The two are unrelated. Neither is really built with the other in mind, their development is not integrated or synchronized in any way, and the paradigms are just generally incompatible. And now, one poses a clear and present danger to the security of the other. 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.