Slashdot Mirror
Ask a Mozilla Person About Firefox 2.0
Last week's interview guest was Dean Hachamovitch, formal title "general manager Internet Explorer at Microsoft Corp." This week we have Chris Beard, Mozilla's Vice President of Products. (Here's a recent "pre-Firefox 2 release" interview with Chris that you might want to look at to avoid duplicating questions.) Chris will be calling on other Mozilla and Firefox people to help answer your questions, but he's the point man here. Slashdot interview rules apply, as always.
What were you thinking with the changes to the tab UI? Everyone who opens enough tabs to trip it hates the scrolling, yet the justification for the feature was based on those who don't open enough tabs. Will it be changed back, or will we forever need to visit about:config on installing FireFox?
As an add on to that question, since you can distribute extensions with the installer, why not just make these "official" extensions rather than building them into the app? Then people could easily switch them off or substitute third party ones (think tab management).
You've created a great extension management system, yet aren't using it yourselves.
I don't know what kind of crack I was on, but I suspect it was decaf.
I'm going to ignore the "practically unusable" part, since there are plenty of people who somehow manage to use it anyway without problems, but you seem to be under the mistaken impression that memory issues are one huge flaw. They're not. They're a bunch of tiny flaws that add up together. It's not like they can go in, fix one bug, and free up half the memory. They have to track down a whole bunch of these things and fix each of them.
If you look at the release notes, nearly every 1.5.0.x release has fixed some memory leaks. 2.0 has fixed a bunch more. They still have more to go, but it's not as if they sat down and said, "Let's ignore the memory leak."