My bitching about Firebird garnered me a link off of Blogzilla which I certainly didn't expect. I replied there to some comments, but I thought it would be worthwhile to reiterate those sentiments here, since not everyone got here via there.

Sure there are other options for my OS, but they're just as victimized by the "let's make a continually experimental browser" idea as Mozilla seems to be.

I'll start by saying that when I posted my list of annoyances, I was completely unaware of the Mozilla Firebird 1.0 Development Charter. I've read it a couple of times and I must say that it scares me. If the Mozilla crew wasn't pushing everyone towards Firebird and away from the suite, I'd have no problem with that document, whatsoever. If you want to recreate IE using Mozilla's goodies, great! Go for it. However, if development of Mozilla proper will cease and all efforts will move towards Firebird, which basically exists to act like IE, then what's an IE hater to do? Making Firebird's keyboard shortcuts and menus, etc behave like IE might be great for converting IE users, but that's no reason to abandon droves of faithful Mozilla/Netscape users who have fought the good fight low these many years.

Apparently my complaint about cache settings was unclear, as many people suggested that I write my applications with cache settings similar to what my eventual end-users might use. I can see someone getting confused, so I'll explain that the application(s) that I write will work perfectly fine regardless of cache settings. However, if I make a change to fix a bug, and Firebird gives me cached results, I think I haven't fixed the bug and this drives me crazy. Yes, I could control caching with HTTP headers and whatnot, but I don't think cache preferences are too much to ask for.