Interviewed by CNN on 29/10/2009 13:01, asmpgmr told the world: > On Oct 28, 4:26 pm, Robert Kaiser <[email protected]> wrote: >> Feel free to try building this version, I'll try to continue our project >> meanwhile, OK? > > Clearly you couldn't care less what anyone else thinks if they don't > agree with you. As SeaMonkey becomes more and more like Firefox + > Thunderbird users will either migrate to them as they are mainstream > and on the forefront of development or they will switch to something > else entirely so you're ultimately doing yourself no favor with this > attitude.
Well, in KaiRo's defense, we're not *paying* him, so we have no right to give him *orders*. He's doing what he thinks is the best thing based on his knowledge of things, including the innards of both the old and the new Seamonkey. The statements I have seen, by him and many others, over the last few years, were that with Seamonkey no longer being an official Mozilla project (and therefore with far less money and manpower available for development) the best choice in the long run would be to make it as close to Firefox and Thunderbird as possible, in order to concentrate efforts in what makes Seamonkey unique, leaving stuff like the development of the Gecko engine in the hands of the Mozilla Foundation. What you were asking was to go back to the old Seamonkey code. Which is old, has known security bugs and is used *only* by Seamonkey, so the maintenance cannot be shared with the larger projects. He prefers instead to keep moving forward with the new code, which *is* shared with the official MoFo projects -- freeing valuable time from the maintenance of obsolete code to do other stuff that needs to be done. If you disagree, if you think you have a better idea of what's the best roadmap for whatever replaced the Mozilla Suite, well, the source code is available, just fork a new project. Maybe you can find enough interested programmers to backport Gecko 1.9 and Tracemonkey back to the old framework, and to maintain it. I wish you success. Personally, I would be happier in the short run if there was a way to use Multizilla with Seamonkey 2. But I understand that this would either involve holding up evolution of Seamonkey, or a massive rewriting job for Multizilla (which the Multizilla author currently has no time for). So for me it's a tradeoff: keep with SM 1.1.18, Multizilla but pass on stuff like a better rendering engine, faster Javascript and such, or move to SM2 and look for other ways to regain the functionality I was used to. So I decided to sacrifice short-term convenience for long-term evolution; I trust that eventually I'll find the right mix of extensions to do the things I used to do with Multizilla. And sometimes change is good to make you rethink the way you were doing things. Losing the Googlebox forced me to find another convenient way to do searches -- and I ended up with a *better* way. I could have used it back in SM 1.1.18, but I was too set in my ways. -- MCBastos This message has been protected with the 2ROT13 algorithm. Unauthorized use will be prosecuted under the DMCA. -=-=- ... Its a dogma-eat-dogma world! * TagZilla 0.0661 * http://tagzilla.mozdev.org on Seamonkey 2 _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
