1 |
felix@×××××××.com wrote: |
2 |
> Something else about this seamonkey vs mozilla conflict has been |
3 |
> bugging me. Why are the two even in conflict? Firefox is not in |
4 |
> conflict with either one. Can't they coexist? |
5 |
> |
6 |
Just take a close look at the history of those two packages and their |
7 |
current status and you should be able to answer that to yourself. |
8 |
|
9 |
The Mozilla suite is what came out after Netscape decided to opensource |
10 |
their communicator. At some point Mozilla devs decided that the codebase |
11 |
was just too complex and rather than fixing it a rewrite would be more |
12 |
appropriate. That's when Firefox and Thunderbird were born (and one or |
13 |
more pther projects whose names I don't remember for sure... Sunbird?) |
14 |
|
15 |
After both Firefox and Thunderbird were somewhat mature the devs decided |
16 |
that it was time to let go of the Mozilla suite. They announced that |
17 |
development of it was dead and there would be no more releases, not for |
18 |
new features, not even for any kind of bugs. Some users of the Mozilla |
19 |
suite were unhappy about that and started a new project which should |
20 |
resurrect the Mozilla suite: Seamonkey was born. |
21 |
|
22 |
Now Firefox was designed to live alongside Mozilla, thereofr the same |
23 |
goes for Seamonkey. But Seamokey and the Mozilla suite are basically one |
24 |
and the same program. It was just renamed at some point and then further |
25 |
developed under the name "Seamonkey". That is why they don't get along |
26 |
that good. |
27 |
|
28 |
Another thing you should be aware of: As development (and even |
29 |
bugfixing) for Mozilla has ceased quite a while ago the last release has |
30 |
a number of security bugs that are well known and wide open. Any program |
31 |
using parts of Mozilla are therefor vulnerable as well. For that reason |
32 |
you shouldn't be using Mozilla and instead switch over to Firefox or |
33 |
Seamonkey. It will be removed from the tree sooner rather than later. |