3 ms·
I'm still surprised they did not just fork Firefox. Did they ever do a write up as to why they went with a Chromium codebase?
by giancarlostoro 3y ago
I'm still surprised they did not just fork Firefox. Did they ever do a write up as to why they went with a Chromium codebase?
- rejectfinite 3y agoGecko is harder to work with and slower. "just fork Firefox" lol Why did Opera, Microsoft, Vivaldi and Brave all base off Chromium if Gecko was so good? *I do use Firefox
- deleted 3y ago[deleted]
- Pannoniae 3y agoOn Firefox I can at least disable most of the isolated processes. I know it's not too secure but at the same time, I enjoy cutting memory usage by 3x, putting an end to the endless RAM consumption of my browser. (I have 32GB before someone says "just get more RAM" or "why do you use the internet with 4GB in 2023". But it still bothers me.) On Chromium I can't do that.
- croes 3y agoBecause Chrome is the new IE and websites are mostly tested against Chromium only. And MS uses Chromium because Google tampered with YouTube to hinder Edge. MS just gave up.
- slig 3y agoDo you know the founder's history? I'd that guess going with Chromium was a big F-you, besides the engine being faster and more modern, of course.
- giancarlostoro 3y agoIt's a bigger F-you to the browser marketshare keeping Chromium at way too much marketshare in the grand scheme of things. I have heard of his history, I would have invested in making a better Firefox fork had I been him.
- soundnote 3y agoThey did start on Gecko, actually. The initial rendering tech was a Gecko-based take on Electron.
- soundnote 3y agoThey actually started with something like a Gecko-based take on Electron, but abandoned it for being too unwieldy. Not sure why they didn't use the Firefox codebase more directly, but it is apparently more unwieldy to work with than Chromium.
- err4nt 3y agoFor disclosure, for my work I must use the stock version of all current browsers so I'm not a fanboy of any one particular browser, and I can't really use forks or ad-blockers. I would bet any money that the reason why they chose Chromium, and did not choose Gecko, was performance-related. Blink is technologically superior to all the others. And between Blink, Webkit, and Gecko: Gecko is the worst-performing choice. I imagine if they did not fork Chromium, they would likely have forked Webkit instead.
- WorldMaker 3y agoThat's a self-fulfilling issue, though. If no one is using Gecko why does Gecko have reason to improve performance. In theory one of the reasons to fork a browser is to add more eyeballs to its codebase. More eyeballs in theory mean more upstream delivered performance patches. If they had good performance engineers it wouldn't matter if they picked the "worst performing", because they could work to improve it and prove they had good performance engineers.
- err4nt 3y ago"That's a self-fulfilling issue, though." It's not self-fulfulling. The state of the Gecko codebase and its performance is not _because_ Brave didn't end up using it. "If no one is using Gecko why does Gecko have reason to improve performance." This question is a valid question, but is unrelated to Brave which does not use Gecko. "If they had good performance engineers it wouldn't matter if they picked the "worst performing", because they could work to improve it and prove they had good performance engineers." It would matter, because they would have chosen the most difficult task which is a sidetrack from the reason they were making a fork of a browser in the first place. The focus of Brave is not to improve the performance of a browser engine.
- WorldMaker 3y agoBrave is a weird example because it included several former Gecko engineers when it started up, so Brave not using Gecko did have some sort of material impact on Gecko. I have no idea if you can quantify how much "damage" was done, but some can be assumed. "Fast" is the second priority listed in Brave's webpage ("Secure, Fast, & Private"), so it is very easy to assume that it was one of their reasons for making a fork of a browser in the first place. It is more than fair to criticize them for taking the ("paved with bad intentions") easy road in that stated priority rather than accepting the true engineering challenge of doing that work on the underdog engine in current last place. (The basic through line of lamenting that they didn't use Gecko: If they had succeeded in that challenge, they would have won a lot more acclaim and done a lot more overall good for the web than anything they have done in forking Blink.)