|
|
|
|
|
by JeanMarcS
3132 days ago
|
|
I don't believe that's the case. Evolution is important. Sometimes you have to get rid of old stuff to get ahead. By doing so, Mozilla shows that it cares about his user. Letting use old stuff that are not maintained anymore (if they are, a compatible version will shows up) lead you to situations like win32 |
|
By completely trashing a tool I'd spent years customizing without anything resembling feature parity ready by release? It's not really on the devs to port something when the new system is missing APIs. The "They had 5 years!" argument directed at the addon devs could just as easily be directed back at Mozilla...
Or perhaps by ignoring the loud negative feedback when I and many others said we didn't want paternalistic "thou shalt not install unless we say okay" controls on add-ons like Chrome has?
Or was it instead by ignoring my repeated questions on how to fix a ten-year-old SSL handling bug that causes a great deal of pain for sysadmins? (Vendors have a poor habit of reusing SSL certs - Firefox will flat out tell you to pound sand and not allow you to visit a site with a dupe cert. Chrome, IE, Opera, and I believe Edge will warn you that this is abnormal, but otherwise continue)
If this is how Mozilla cares for its users, I'd hate to see what they consider neglect.