5 ms·
I wonder if they are driving people away by disabling things that worked for years. At work I have to use Java and Silverlight. In addition our IT department do
by maxxxxx 10y ago
I wonder if they are driving people away by disabling things that worked for years. At work I have to use Java and Silverlight. In addition our IT department doesn't seem to be able to keep their certificates up to date. With chrome and Firefox being so strict they are almost unusable so I am using IE. In theory this should pressure suppliers to get rid of Java and our IT department should have better certificates but in practice I don't see this happening.
- simion314 10y agoI discovered now you need to have your extensions sign by Mozilla, we had such an extension that worked only with our product, you needed an account and we did not had many users, but now the extension will not work(you can make it work only on dev version of Firefox) until we get it signed by Mozilla.
- callahad 10y agoYou can automatically sign your add-on by calling `jpm sign` (SDK add-ons), `web-ext sign` (WebExtensions), or by manually hitting our API: https://developer.mozilla.org/en-US/Add-ons/Distribution#Signing_API https://developer.mozilla.org/en-US/Add-ons/Distribution#Sig...
- apostacy 10y agoRequiring signing of web extensions is still ludicrous. It makes sense for Google to do it. It makes zero sense for Mozilla to do it. Google wants to make money by developing a platform. Mozilla (should) want to make technology that empowers people. Mozilla does not have to provide technical support. Mozilla isn't making money off of it. I think that the only reason they did it was because Google did it. Should emacs or Autocad require signing of extensions? Why not? Because it would go directly against the grain of what those tools are for. And users should be smart enough to handle their own security. I would like someone to justify Firefox extension signing, while also explaining why nobody cares if other software has signed extensions.
- kibwen 10y agoBecause web browsers are the single largest and most common attack vector on every end-user device, and emacs and autocad aren't. I'm not in a position to say whether Mozilla's implementation of extension signing makes any sense, but it is practical to hold web browsers to higher standards. I'm also not sure how extension signing makes Google any money?
- apostacy 10y agoExtension signing makes Google money because it supports their platform infrastructure. It supports things like Google Play. Microsoft also made money from Internet Explorer, even though they didn't charge money for it. They benefited from controlling the platform. Mozilla has no such incentives. And they also don't have any larger strategy that Firefox supports.
- tempay 10y agoUltimately I think someone has to else people will never stop using Java and your IT department will never improve. At least currently it seems like all the main venders are unified in progressing so maybe one day we can instead start complaining about something else, like how outdated html5 is.
- simion314 10y agoDo you think someone will approve that developers rewrite the Java/Silverlight app or the alternative to use the old/LTS browser and have devs work on current bugs and new features(that could be on a different project not the Java/Silverlight one that is currently in maintenance mode)? I think the second option will be used in most cases.
- NiLSPACE 10y agoI see people on Reddit saying they'll leave to Chrome if XUL extensions will no longer work since Chrome would be faster than Firefox, but I don't think they understand that Mozilla is removing XUL extensions so that they can finally make Firefox faster again. And even if this wasn't the case Firefox is still way more customizable than Chrome. I think that as more and more websites will move away from Java and Silverlight I expect that other companies will be forced to do the same as the customers will keep having less reasons to keep a browser with those plugins supported.
- staticassertion 10y agoYeah, the other side of all of this is that I'd leave Chrome for Firefox if it did drop XUL and get up to par performance/ security / feature-wise. I'm sure many others feel the same.
- dblohm7 10y agoYeah, I think our big bet here is that Firefox will achieve better market share by leapfrogging the competition in performance versus remaining insanely customizable despite lower performance. EDIT: Added "insanely"
- maxxxxx 10y agoI am not the product manager so I don't know for sure but this can go very wrong. Once you disable something and force a user to go somewhere else they will probably not come back. Especially since Chrome and Firefox and to some degree IE are in a race to almost look the same and have no distinguishable features. It used to be that Firefox's selling point were extensions. With that lost, what's the reason for Firefox? I don't think performance matters enough for most users to switch.
- staticassertion 10y agoIt's not like every Firefox extension will be broken. And I'm an ex Firefox user who switched to Chrome for the sandboxing and multiproc architecture. I'll happy go back to Firefox, I'd much rather use a browser by Mozilla over Google. Maybe in the short term keeping some users is worthwhile but they'll continue to lose them slowly to Chrome, and browsers aren't fighting a short game. Firefox, Chrome, IE, they're not going anywhere - they've been around for a long time with plenty of market share. It makes sense to be forward thinking here.
- aanm1988 10y agoAlternative, is it worth it to try to cater to users like "you" vs just leaving them behind? Java and Silverlight I get, but not upgrading certs I consider to be pushing it. When we cater to users who have no interest in upgrading technology we hold everyone else back. I prefer the technique of saying "It's done on this date. Ignore us at your peril". The view that technology can just be bought and then never maintained is ridiculous and should die. Nothing else operates like this. You buy a machine and you know it's going to include ongoing maintenance costs. Software is no different and trying to pretend it is just ends up with you paying stupid amounts of money and resources to maintain an ancient tech stack decades later. Or worse you have a stack where the people you are paying big money to maintain it are starting to retire or die.