chromium VS brave-browser

Time to dig out my Wyse 50 again! https://chromium.googlesource.com/chromium/src/+/HEAD/docs/o...

Thanks. Yes, rendering and shaping are distinct but some of the linked libraries did one, the other, or both and the parent commenter singled out rastering which is how I ended up putting FreeType and HarfBuzz in the same sentence. Even then both are commonly used in tandem (see [1]-[9]) and have a few overlapping functionalities.

> it does support BiDi, complex script shaping

Hey, that is indeed quite good. Would you mind if I ask you how well is the support for popular Asian languages?

> linking C and Rust in WASM is unfortunately not really possible

Damn. I am not very experienced in Rust but I would not have guessed that. I apologize if I misrepresented difficulties related to targeting WASM.

[1] https://github.com/apple-oss-distributions/WebKit/tree/WebKi...

[2] https://github.com/apple-oss-distributions/WebKit/tree/WebKi...

[3] https://github.com/chromium/chromium/tree/main/third_party/f...

[4] https://github.com/chromium/chromium/tree/main/third_party/h...

[5] https://searchfox.org/mozilla-central/source/modules/freetyp...

[6] https://searchfox.org/mozilla-central/source/gfx/harfbuzz

[7] https://cs.android.com/android/platform/superproject/+/maste...

[8] https://cs.android.com/android/platform/superproject/+/maste...

[9] https://www.amazon.com/gp/help/customer/display.html?nodeId=...

The word "Zygote" will actually be really clear to anyone who's been exposed to Chrome's multiprocess architecture.

https://chromium.googlesource.com/chromium/src/+/HEAD/docs/l...

> A zygote process is one that listens for spawn requests from a main process and forks itself in response. Generally they are used because forking a process after some expensive setup has been performed can save time and share extra memory pages.

With that background, --zygote isn't actually a flag at all. If you click on it it takes you to a string constant, but that string is actually a value for the --type flag. e.g. an unsandboxed zygote process would have `--type=zygote`.

`--type` is itself an internal flag, explaining it's lax description of "Flags spied upon from other layers.". However it is briefly described in the documentation I linked above.

Chromium license is permissive: https://github.com/chromium/chromium/blob/main/LICENSE

Brave isn't just based off of open source though. It is open source. Here's the entire source code - https://github.com/brave/brave-browser

1.47.171

Brave Github repository

That's literally untrue. Micrsoft had made >1600 commits as of 2020. They are actively involved in Chromium development. Additionally, they don't have to "own" it. It's completely possible to support a fork just like Brave will be doing. I'm not going to assume your occupation/areas of interest, but I do work in software and this is just how Open Source Software works.

which will be in 2024 for full rollout, and also major forks will hardcode adblockers, not using the manifest API to get around it. also Brave will allegedly always support v2

https://github.com/brave/brave-browser/issues/15645 https://github.com/brave/browser-laptop/issues/13880

You can easily find on github issues that even talk about Only make requests to *.rewards.brave.com endpoints after Rewards opt-in so it is obvious you didn't reset it like bat-chriscat said.

www.brave.com