Comment What's the plan, Stan? (Score 1) 408
It would be helpful if there were a (high-level is OK) product plan for Firefox, Thunderbird, and Seamonkey. A quick glance/search did not reveal such a plan. What are the driving factors influencing development?
Personally, I think any substantive change should come with a migration strategy. I.e., if you are going to change the way plugins are handled, then also provide a way for me to migrate all of my plugins to the new format. (I shudder to think of all the coding and testing hours which were simply discarded when Firefox made the old plugin model obsolete. I'll bet no developer has added those hours up when implementing a change.)
I also think that users should be given choices: If I like a capability and you don't, that's fine. But rather than shoving a change down my throat, give me (and you) the option of turning it on or off. That way we're both happy.
One final comment: I agree with the general sentiment that the Firefox/Thunderbird/Seamonkey development team is arrogant and out of touch with the needs of many users. A little more of, "What do you think of this?" would be enormously helpful.