Before you come at me with stuff like Librewolf, Waterfox and IceCat; those don’t count. They are just tweaked Firefox distros with mostly basic low level changes. Not every Chromium browser is super unique either, but I feel like there are more differences between them then there are with Firefox distros. Why is that? Why there aren’t different browsers that use Firefox’s engines but provide a different UX?
Yeah, I have heard before that one reason is Chromium being more modular.
I also assume Google put somewhat of a focus on that, after Node.js chose Chromium as a base. If I remember correctly, it was initially not possible to run Node.js in a headless mode, which it is now.
So the Chromium is more modular, I always guessed that it was but not certain. Thank you for your answer
These days, yeah, I’m pretty sure that it is. One of the stated goals of Servo was that it should have a well-defined API to allow embedding into Node.js and similar.
But a few years ago, when people started embedding browsers into everything, that difference might’ve been less big between Firefox and Chromium.
So, maybe there was another motivation, for example Chromium’s JavaScript engine had much better performance around that time, which might’ve been rather important to Node.js.
Not. Google put effort in making WebKit less modular in blink. In WebKit you can chose the renderer, while in blink you ate stuck with skia.
Blink is a black box widget you van interact only via we extensions API. WebKit is a set of libs you can meddle with.
For instance, there is no way to render a web page to a PNG file in blink, while it’s trivial with WebKit.
EDIT Alas, the first chromium was WebKit with the js engine replaced by V8. Not sure if you can chance blink js engine.