On 2011-08-08 10:17, sean nathan bean wrote:
Pat Connors sent me the following::
Okay, I just got home after a week away and see there is another new
version of SM. I am still on 2.0.14 and didn't update to 2.2 because of
all the complaints. Now we have 2.3 and more complaints. I really don't
know what to do. I like the version I am using. I am using Windows 7
which seems to complicate all new program updates.
Just wondering how others using Win 7 have managed with the new update.
my two cents:
SeaMonkey 2.1 and 2.2 have been virtually flawless...there may have been
a few niggling details which irked me personally... but none rose to the
level of making me decide to remain in the insecure 2.0.x series...
Sorry to disagree with you, but I found 2.1 and 2.2 to be virtually useless
because they were so badly flawed. Add the irreversible database changes to
this and I'm not even going to try 2.3.
I am very sad that SeaMonkey has chosen to follow on with the FireFox
release program (I understand that SM is inextricably tied to FF) rather
than just maintaining the 2.0 tree. I (and many others) believe the FF
6-week release cycle is an extremely bad idea and I have no intention of
going that route. Despite being a Netscape/Mozilla Suite/SeaMonkey user for
almost 20 years, I'm afraid I'm going to have to ditch Mozilla in all its
forms and go a different direction. Since I have a large collection of tools
I've developed for hacking various things about Mozilla, I do not do this
lightly. To put it bluntly, I am not interested in a SeaMonkey that is
nothing more than FireFox and Thunderbird launched simultaneously -- if SM
can't offer something other than this, there's no reason for it to exist.
For me, it is far more important that I have something that is stable and
has a stable database format that I can develop my own tools for than it is
to support the latest "eye-candy." The database format for bookmarks and
mail has been almost unchanged for that entire 20 years -- until now.
I haven't decided which browser+email I will be switching to since
considerable research will be required, but it has become sadly obvious to
me that it is necessary to change. Unless, that is, someone is willing to
fork SeaMonkey at the 2.0.14 level and maintain it strictly with security
bug fixes.
_______________________________________________
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey
