i used to use Hexchat cause it was easy to setup an not bloated wikth useless shit i dont need . i use Adiirc now, but i still keerp an eye on Hexchat. last time i got a file from someone in irc was back in 1999 , i was on Dialup then an he was on Cable. if my Memory serves me right, i think he was sending me Norton Utilities

but back then i used to go around a lot of Warez irc channels an Porn. so i had something to give back to someone

the era of fserves was magical, indeed

my trilogy was: music on Red Latina, ROMs and cracks on EFnet, and years later, anime on Rizon

do not miss fserve/DCC bot queues, tho :D

On windows I think the last ones I've used were Xchat (so Hexchat?) and ChatZilla

I don't think I've ever used MSCC as an actual main IRC client

Is Googletest not the reason why you can't compile a build for Windows XP?

Loglandia[m]: reason for no longer supporting Wndows/pis that 64-bit Windows/XP is a shit show so only reason to suupport Windows/XPis to allow building on 32-bit hardware which can really not run what is expected to be able to do with a Web browser.

Loglandia[m]: I did once have an old 32-bit cpu and waws running linux with a non-gnome desktop.

Loglandia[m]: if you absolutely need SeaMonkey on a older computer that can't run a 64-bit OS (and can't have its RAM expanded for whatever reason), at least consider migrating it to Linux

XP builds of newer versions are simply NOT HAPPENING, the technical reasons behind it are pretty clear

as for retrocomputing, retroboxes should stick to retrobrowsers (despite Clownflare and Google's attempts to kill vintage Internet)

You told me 0 technical reason.

not me, but the actual developers here have done so

They*

for me they did

"incompatible 3rd party libraries" is a heavy one

"compiler limitations" is another heavy one

Yeah, 0 titles of 3rd party library. I asked 2 and got answer: "This is not needed to compile a build for XP".

...have you ever compiled a web browser, or any other complex project ever?

I play in divintion.

* I play divintion.

it's enough to take a look at each source repository

if you want to dig deeper, each commit in each repository has messages which tell you the changes

you can start your research there

So, you confirmed that Seamonkey developers don't know why they does not compile Seamonkey for Windows XP.

*sigh~*

I suspect that if I start research I will detect an stupid reason again.

I have seen a not needed code, but reason was: "Because it's "modern, fashion"." And they don't care that it was at 3-4 slower.

here is something YOU can try at home

seamonkey-project.org/dev/code-development start here

clone the repo, and try building it yourself

then figure out why it doesn't run on XP

like "OK, i need to tweak this compiler setting"

then it blows up for a completely different reason, and then you quickly descend into that rabbit hole

(I know, I've been there on completely unrelated projects)

I must warn you of something: web browsers are very complex beasts, and you're pretty much on your own

not trying to discourage you, but if you're hellbent on a XP build, you should start walking the path yourself

Loglandia[m] Install VS2017 and needed dev libaries (needs Windows 7 x64 and 8GB memory at least), then backout everything which sets a Windows target > XP, they fix and adapt third party libaries and code. Shoud be easy and then you can run it and you can let us know how it works out. Might be 2029 or I suspect never. You have zero clue about development and these statements that it can be...

...done pretty easy are starting to get on my nerves. If you want to continue with them look for another channel for these rantings soon.