chromium VS ungoogled-chromium

As for the second idea: I don't know the details of MSDelta, but updating references when the code moves is more clearly represented by a newer format Chrome has been using called Zucchini [1]. Courgette does a complex process of disassembling (into several binary streams), aligning labels, and sending a patch of the disassembly, so the patcher has to do disassembly, patching, and reassembly. Zucchini does a more straightforward disassembly pass to note where the references are, and then patches them based on how it knows the code moved. Compared with Courgette, this involves less intermediate state so it's faster [2], the code is simpler, and because much more is implicit in the code motion the patches tend to be smaller.

That basic technique goes back at least to the TranslateAddress method in Exediff (1999) [3].

I've been meaning to write up an article on this stuff [4], Google doesn't seem interested in publicizing Zucchini themselves, maybe due to the patent kerfuffle around Courgette. Microsoft's document on delta compression [5] covers a lot of this ground.

[1] https://chromium.googlesource.com/chromium/src/+/HEAD/compon...

[2] Some of this can be avoided, I made some changes to Courgette for a significant speed increase here: https://bugzilla.mozilla.org/show_bug.cgi?id=504624#c39

[3] http://robert.muth.org/Papers/1999-exediff.pdf

[4] I did write up a bug to consider this in Firefox, with patch size comparisons, but ultimately we didn't switch from the simple power of bsdiff: https://bugzilla.mozilla.org/show_bug.cgi?id=1632374

[5] Their system can use info from the pre-linked objects and PDB symbol files for better alignment, I'd played around with seeding alignments like this in bsdiff and Zucchini but I don't recall it giving significant improvement. https://docs.microsoft.com/en-us/previous-versions/bb417345(...

Last I heard, Courgette is deprecated (and replaced by Zucchini) [0].

[0] https://chromium.googlesource.com/chromium/src/+/HEAD/compon...

> I don't think there s a static linking going on there, else it would be impossible to use Electron for closed source software.

no, the closed source part can stay closed source but linking must be reallowed.

Just run "strings" on the code binary: you'll see symbols coming straight from Blink like this one: https://github.com/chromium/chromium/blob/72ceeed2ebcd505b8d...

    $ strings code-insiders | grep HTMLFormControls

https://github.com/chromium/chromium/search?q=visitor

And the list goes on, and on.

This is true for V8, which underlies NodeJS, and is the engine that powers most modern JavaScript:

https://github.com/v8/v8/search?q=factory

V8 was designed by the same engineers who built the Java Virtual Machine, and what techniques did they employ to build this massive piece of software that runs the modern web? Object oriented design, and design patterns.

It's very probable people designing modern web applications for the FAANGs are not particularly aware of design patterns, or even maybe that MVC is a design pattern even if they are using it. It's possible many design patterns aren't useful for the types of problems they are solving, or could complicate matters if they used them haphazardly.

But the engine driving every single JavaScript program, is built on top of a behemoth of object oriented, design pattern laden, software, written by FAANG engineers that I promise you understand design patterns extremely well.

I'm not saying this is the end all, be all, of software design. Or that "modern" functional takes on software design (most functional languages and ideas predate OOP) aren't perfectly valid, or successful. Or even that they couldn't solve many of these problems.

I'm just contesting any dogmatic rejection of what has actually been one of the most successful branches of software design.

Chromium has "Paint Preview" (aka "Freeze Dried Tabs") [0] which basically does this. I think it's only supported on Chrome for Android right now.

[0] https://chromium.googlesource.com/chromium/src/+/refs/heads/...

Bromite uses a compiled blocklist format (DAT). You'll notice that the default blocklist is called filter.dat. If you want to compile your own list, HERE are the instructions.

kalo di desktop pakai Ungoogled Chromium + uBlock Origin

Ungoogled chromium is my second recommendation

I've been using Brave on Windows but, just started testing Iridium Browser (the EFF Cover Your Tracks results are okay). Maybe Ungoogled Chromium next.

I am not too well versed in the Chromium based landscape. In addition to Vivaldi and Brave. Vivaldi is mostly open source but not fully and thus you can't compile it from source and thus have complete trust without reverse engineering. Brave seems to be but I haven't inspected closely if there are any closed source dependencies. For development purposes I typically run ungoogled-chromium, but I haven't looked at how to keep it updated on Windows installations.

It's worth noting that Ungoogled Chromium has some security flaws, as well as a few privacy features, such asCNAME decloaking and Ephemeral Third-party Site Storage, that, as far as I know, are not available. To be honest, keeping Brave and disabling all the "crypto crap" would be a better option for the OP.