Steve Dunn wrote on 24-12-18 16:19:
On 2018-12-23 19:04, Nuno Silva wrote:
On 2018-12-22, [email protected] wrote:
[...] Because without an up to date engine Seamonkey
will not be able to appeal to new users and long time users will
slowly move on as well. I.e. in my optinion Seamonkey would not have a
future without an up-to-date engine.
Are you really sure nobody would be interested in Seamonkey if it does
not chase Firefox?
It doesn't necessarily have to chase Firefox, but it has to be up
to date. Think back to when Seamonkey 1.x fell a couple of years
behind Firefox while Seamonkey 2.x was in its prolonged gestation.
More and more sites didn't work properly in Seamonkey 1.x because it
hadn't kept up with modern standards. That's what's going to happen
to Seamonkey if it doesn't get up to date.
Maybe the best solution is the massive amount of work required to
make Seamonkey compatible with a current version of Gecko (the engine
it shares with Firefox). Maybe the best solution is the massive
amount of work required to rip Gecko out and replace it with something
else (Chromium or WebKit or whatever). Or maybe the best solution is
something else. But simply leaving it with the current engine is not
a viable option; that will result in Seamonkey gradually becoming
unusable as it gets left behind.
I totally agree with you, but do you think that a group of volunteers
will be able to take this big step?
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
