Firefox keeps bugs unpatched for over 9 years

To give an example, the annoying "FTP server 215 ... is currently unsupported" message. This lingers from the way the old Mozilla (pre-Firefox) recognized FTP listings.
https://bugzilla.mozilla.org/show_bug.cgi?id=202730
Unsupported FTP server "xxxxxxx" after login and SYST command
https://bugzilla.mozilla.org/show_bug.cgi?id=277827
Unsupported FTP server "ITRON embedded printer OS"
This bug was reported in 2003, with various duplicates since then. They know what's causing the problem. Somebody sent in a patch and they still haven't fixed it. They're more concerned with bumping up the version numbers than a few simple bug fixes.

>>66
Firefox developers should write and test their code on a machine from ~10 years ago with limited memory and CPU power. That would be much better as if they get acceptable performance on such a platform, FF would be bloody fast on a typical machine today. Then they probably wouldn't have such idiotic ideas as writing the bulk of the UI in JS.

Somewhat more relevant bug that is still open (and has been since 2000):
https://bugzilla.mozilla.org/show_bug.cgi?id=38966

One of the things that's always irritated me about FF is how difficult it is to configure. about:config is not that much better than editing the text config directly --- how hard is it to make it a treeview, since that's obviously what the config structure is? And as it turns out it does let you set per-site security configs BUT those settings are not even shown in about:config, you MUST edit the text config directly (WTF!) and the work to add a UI for it (IE and Opera had one long ago) "may be the hardest part of the feature to implement" according to them (double WTF!)

http://security.mozdev.org/ <- they started on it, then stopped and it's still "incomplete".

For fucks' sake, what is so bloody hard about making a UI that just manages those settings? If you think that's hard, how in hell have you managed to change the entire goddamn UI and add tons of frivolous bloaty HTML5 support crap over these years? Someone has added a patch for a suggested UI to the bug, but it's not been put in. You often ridicule IE because of its security and advertise your browser's security as superior, but why does security-related stuff like this not get done? "Take back the web" my arse. IE has security config that works, even if not all that well. Mozilla, get your act together.
</rant>