"There is only SeaMonkey"

I don't think SeaMonkey supports WebComponents yetjoydivision47 wrote: ↑2024-07-27, 02:46I'd say PM is a lot less "legacy" than Seamonkey in most aspects.![]()
I personally don't mind Seamonkey, used to use it a bit. But it broke a lot more on websites than Pale moon ever did.
I sometimes use Composer to quickly create tables
I just never could get into SeaMonkey, because it wasn't interesting to me. I mean... if my e-mail client crashes when the browser does, how is that any better than just having a tab for webmail? I don't know. I mean, I guess in some ways we owe SeaMonkey a debt of gratitude for being the first project to ever attempt to diverge significantly from Mozilla. Without having learned from their mistakes, we might never have gotten as far with this project as we did.joydivision47 wrote: ↑2024-07-27, 02:46I saw this a week ago
"Legacy PM Sources" made me giggle, really? I'd say PM is a lot less "legacy" than Seamonkey in most aspects.![]()
I personally don't mind Seamonkey, used to use it a bit. But it broke a lot more on websites than Pale moon ever did.
I can respect them for actually going in their own direction and their dedication to holding out, rather than just following Firefox and Thunderbird.athenian200 wrote: ↑2024-07-27, 09:14I guess in some ways we owe SeaMonkey a debt of gratitude for being the first project to ever attempt to diverge significantly from Mozilla. Without having learned from their mistakes, we might never have gotten as far with this project as we did.
Well, I'm not sure if that holding out was actually dedication or just the reality that their resources are very limited and can't follow FF and TB into e10s and abandoning XUL (which they wanted). They've tried to rebase into Firefox 60 for SeaMonkey 2.57 which would've killed XUL, brought in full WebExtensions support, and introduced e10s, but they eventually decided in their 15 January 2023 meeting that it no longer makes sense to pour resources into making 2.57 actually happen. It's just too much effort; WEs are made with the Australis (and later on Photon and Proton) UI in mind which SM obviously didn't have, and e10s is made tricky by the fact that they're not just a web browser (it took years for Thunderbird to even get e10s despite having rebased to mozilla-esr60+ IIRC). However, despite that they still act like they will be making a new version based on the latest Mozilla codebase, as evidenced by their wiki homepage.joydivision47 wrote: ↑2024-07-27, 11:04I can respect them for actually going in their own direction and their dedication to holding out, rather than just following Firefox and Thunderbird.
joydivision47 wrote: ↑2024-07-27, 11:04Off-topic:
Yeah! I like your Mima avatar!!
I should check out the PC-98 games again, haven't really played much Touhou in the past couple of years.![]()
Wasn't it the other way around? SeaMonkey was there first and was Mozilla's initial foray into open-sourcing Netscape, and it was Firefox that forked off and became their focus to put all their resources in later on...athenian200 wrote: ↑2024-07-27, 09:14I guess in some ways we owe SeaMonkey a debt of gratitude for being the first project to ever attempt to diverge significantly from Mozilla.
Oh i forgot about that.jobbautista9 wrote: ↑2024-07-27, 11:46Well, I'm not sure if that holding out was actually dedication or just the reality that their resources are very limited and can't follow FF and TB into e10s and abandoning XUL (which they wanted). They've tried to rebase into Firefox 60 for SeaMonkey 2.57 which would've killed XUL, brought in full WebExtensions support, and introduced e10s, but they eventually decided in their 15 January 2023 meeting that it no longer makes sense to pour resources into making 2.57 actually happen.
jobbautista9 wrote: ↑2024-07-27, 11:46Off-topic:
Haha, glad to know I'm not the only Touhou fan here!And tbh I've been wanting to change this avatar to another Mima since it's supposed to have been for Christmas season only, but I'm lazy and she looks really cute here lol
I think at some point in the middle they did realize they will have to keep XUL overlay add-ons support alive for a bit longer when 2.57 was still being developed, since rewriting every single part of the UI to not use XUL is going to take forever.. And there is some precedent to this in another non-Firefox project which is Thunderbird where they did keep some support until version 78 (though their way of doing it from version 68 which is an "overlay loader" looked more like a hack)joydivision47 wrote: ↑2024-07-27, 14:08First time i read it I thought that they were gonna try and do something like Waterfox classic and keep XUL while adding WE support, rather then getting rid of it. In that case I retract what I said earlier if they're trying to get rid of XUL from their browser
That seems like the only thing guaranteed to be kept, yes. And probably what doomed the whole 2.57 effort if UI also means the entire suite (i.e. including the mail, IRC, Composer, etc.)
Nope, they disabled it by default. During development towards 2.57 they had to turn it off in about:config when mozilla-central flipped it on in their libpref: https://bugzilla.mozilla.org/show_bug.cgi?id=1410614joydivision47 wrote: ↑2024-07-27, 14:08As for e10s, I thought they had already introduced that? From what I know Seamonkey is multi-process (Unless e10s specifically means the multi-processing Firefox Quantum uses, I wouldn't know lmao).