Blink is a fork of WebKit wich is a fork of KHTML, KHTML exist since the '98, the codebase isn't that younger too. Was tweaked by Apple then by Google, with some features that don't exist on other engines.

Blink has a younger code base that’s easier to build on. Gecko has been around since the early 90s and has some ancient evils lurking deep within.

They both are of very similar age actually. The old Netscape rendering engine originated in the early 90s, but Gecko was a rewrite from scratch that was first used in a browser in 1998.
Blink is based on KHTML which is based on khtmlw, which was written at some point in the mid-90s, but as well saw a complete rewrite in 1999.

The only time I ever had memory problems with Firefox was when I tried to run it on a potato. That complaint has always been bullshit.

Edit to add: The aforementioned incident was in 2010, on a machine with only 512MB of RAM. Like I said, potato. Chrome back then was somewhat more memory-efficient than Firefox, and could support three open tabs on that machine before it started thrashing, whereas Firefox would thrash with just one. Both browsers performed abysmally under such a severe RAM shortage, but Chrome was slightly less abysmal. Slightly. I seriously doubt the current version of either browser would be usable on that machine, although I don't have it (I gave it away soon after this incident) so I can't check.

Faster than chrome ? Do you have any source ?

Gecko was probably based on early 90s code but it wasn’t out until 2000. It’s still older than almost everything else though.

Ah, yeah, and it's probably too laborious to change the browser base now.

Thank you for your answer! :D

Oh, I see. I had an internship last year where I developed a WebApp and I only got a slight glimpse of the differences between Blink & Gecko but even that already influenced my code so I can kinda imagine the struggle :')

Thank you for your answer! ^^

I don't know if I'd say separating Gecko from Firefox is all that difficult. About a decade ago I worked on a project at the tail end of my internship at Mozilla to separate Gecko from Firefox Mobile. The idea being to create a sort of GeckoView Android component that could be used like a WebView component to give devs the option to embed Gecko in their app rather than (at the time) WebKit and for Firefox Mobile to become a UI wrapper around a GeckoView component as well. I only had a few weeks to work on it and in that time I had a rough proof of concept running which was an independent Android app that ran Gecko through this new GeckoView component and had a super basic UI to control it. Unfortunately being an internship project I didn't have time to take it through to completion and being the Firefox OS days at the time the team had other priorities so I don't believe it ever got fully finished. But point being is that it's not terribly difficult to separate the two; I did it as an intern in a few weeks a decade ago.

Ah, so it isn't really built do be adapted by others the way Chromium is. Well that's too bad. At least there's Floorp although I don't really have the knowledge to actually check whether their code is fine or not (as they are quite unknown yet) so I'm not so sure whether to trust them.

Anyways, thanks for your answer! :D

Oh, thanks for linking it. Gonna read the replies you got too :)

Edit: I linked your post in my original question :D

Link seems to lead to a us politics post for me rn

We can go further. Just recently I saw a website that supposedly "is best viewed full screen, 800x600 or better, in Netscape"

And I am convinced people didn't think the same would happen when everything other than Firefox and Safari switched to being based on Chromium because "nah, it's open-source, that won't happen."

Well, here we are. The only thing keeping Chrome from completely dominating is that iOS currently requires all browsers to use WebKit, but once there is a real Chrome on iOS, you know every site is going to tell iPhone and iPad users to "lol just download Chrome."

This is not the situation I was hoping for, but I saw this coming years ago.

And that's the problem. It gives full control power to Google. That's the reason that popularity needs to be broken.

Seems fair, tho 99,99% of websites are working just fine

Thank you for your answer :)

Oh, interesting, thanks for the insight :)

Apple didn’t “decide it’s better to use webkit”, they MADE WebKit (from forking KDE). Back when they started WebKit Gecko was only out for a year and heavily associated with Netscape, while KDE’s was already mature