chromium VS ungoogled-chromium

btw, if you want to speed up the build times you should look to use RE API or Goma. it can make a build finish in about 15 to 30 minutes.

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

It seems like gemini 2.5 is pre-trained on chromium given it has a lot of context into the current state of the codebase. That may help a bit.

Also, I've not tried this yet, but maybe using an MCP server over a clangd language server is a solution to the context problem?

https://chromium.googlesource.com/chromium/src/+/master/docs...

Looks like it's still vendored by Chromium: https://github.com/chromium/chromium/tree/main/third_party/c...

It does happen, but it's pretty rare compared to Windows in my experience, where inconvenience is essentially guaranteed.

Firefox on Linux did not really enjoy being updated while running, as far as I remember; Chrome was fine with it, but only since it does some extra work to bypass the problem via its "zygote process": https://chromium.googlesource.com/chromium/src/+/main/docs/l...

Standard operating procedure for both the Chrome [https://chromium.googlesource.com/chromium/src/+/HEAD/docs/s...] and Firefox [https://www.mozilla.org/en-US/about/governance/policies/secu...] bug tracking systems.

But the fix itself is public in both the Chrome [https://chromium.googlesource.com/chromium/src.git/+/36dbbf3...] and Firefox [https://github.com/mozilla/gecko-dev/commit/ac605820636c3b96...] source repos, and it makes pretty clear what the bug is.

My starting point would be Chromium's documentation, as - presumably - chrome is one of the most widely used and battle tested, user-facing, third party sandboxes running on end user machines.

Windows: https://chromium.googlesource.com/chromium/src/+/main/docs/d...

Linux: https://chromium.googlesource.com/chromium/src/+/main/sandbo...

OS X: https://chromium.googlesource.com/chromium/src/+/main/sandbo...

With the caveat that I wouldn't necessairly assume this is the cutting edge at this point, and there might be other resources to invest in for server-side sandboxing involving containers or hypervisors, and that I've only actually engaged with the Windows APIs based on that reading.

I wrote `firehazard` ( https://docs.rs/firehazard/ , https://github.com/MaulingMonkey/firehazard/tree/master/exam... ) to experiment with wrapping the Windows APIs, document edge cases, etc. - although if the long list of warnings in the readme doesn't scare you away, it'll hopefully at least confirm I hesitate to recommend my own code ;)

It's ok if something doesn't look familiar at the moment. You should google it right away. Or check some source code of v8.

The source is available: https://chromium.googlesource.com/chromium/src/+/refs/tags/1...

It’s not “training an AI model on screen contents without consent.”

It is a stupid feature for Google to enable by default: likely what’s making OP’s machine useless is that it’s running an OCR inference model on the OP’s images to index them for search.

Go to chrome://flags and disable “Enable OCR For Local Image Search” and I bet the problem goes away. The AI Service does have a few other features, but that’s the one that’s likely to be cooking the machine.

As for the other comments on this thread, I doubt there’s anything to do with GDPR here. It’s all local.

The license was explicitly chosen to enable code sharing with LLVM's libc++ (https://devblogs.microsoft.com/cppblog/open-sourcing-msvcs-s...).

The MSVC STL's quality is good enough for thousands of pieces of Windows software (including Windows itself & Microsoft's software such as Office) to depend and rely on. It delivers excellent performance for a broad range of use cases. It is actively developed in the open, delivering cutting-edge (C++23 & C++26) features, accepting Pull Requests and wonderfully documented on GitHub. It can be consumed using MSVC and LLVM clang-cl (which the MSVC STL maintainers test with CI infrastructure). The maintainers are actively working on "hardening" features to enable more secure C++ (https://github.com/microsoft/STL/wiki/STL-Hardening).

Unless you specify what "best" or "a library's quality" means to you, MSVC STL is excellent and because of that, the default choice on & for Windows.

Google chooses to only support libc++ for Chrome/Chromium (https://chromium.googlesource.com/chromium/src/+/main/docs/t...). libc++ is not a Google-owned project.

Chromium is Chrome with "less" (but, still substantial) Google. ungoogled-chromium[1] is Chromium with no Google.

[1] https://github.com/ungoogled-software/ungoogled-chromium

What's the best next choice if I don't want to move away from a Chrome-like experience?

(Old habits die hard)

There's https://github.com/ungoogled-software/ungoogled-chromium - is it a sound choice nowadays?

https://github.com/ungoogled-software/ungoogled-chromium/blo...

I think you want:

https://github.com/ungoogled-software/ungoogled-chromium

Without signing in to a Google Account, Chromium does pretty well in terms of security and privacy. However, Chromium still has some dependency on Google web services and binaries. In addition, Google designed Chromium to be easy and intuitive for users, which means they compromise on transparency and control of internal operations.

ungoogled-chromium addresses these issues in the following ways:

* - Remove all remaining background requests to any web services while building and running the browser*

* - Remove all code specific to Google web services*

* - Remove all uses of pre-made binaries from the source code, and replace them with user-provided alternatives when possible.*

* - Disable features that inhibit control and transparency, and add or modify features that promote them (these changes will almost always require manual activation or enabling).*

Cromite[0] is the best on Android, it's a privacy-oriented open source patchset on top of Chromium.

Cromite has a desktop build, but it's a bit more experimental than the mobile build, so you can use Ungoogled Chromium[1] instead. Ungoogled is also a privacy-oriented open source patchset on top of Chromium. Check the beta flags to enable some more interesting features like getClientRect anti-fingerprinting measures (unfortunately breaks some React-based sites that go into infinite re-render loop).

Both of these browsers selectively include patches from Brave, but they are community-oriented builds so imo more trustworthy than Brave, which continues to package various shady anti-features and always will because it's backed by a for-profit company.

LibreWolf[2] is the nicest Firefox-based one for desktop, I think. It's pretty hardcore, though, I most only use it to visit mainstream social media sites.

I tried a bunch of the Firefox-based ones on mobile and none of them clicked for me. Cromite is just too slick on Android. Put the address bar at the bottom and off you go. Only downside is no online syncing of tabs and bookmarks, but meh. You can save all open tabs to bookmark bar in one hit then export your bookmarks, send the file through whatever E2EE channel you want to your other device and import then reopen them again.

[0] https://github.com/uazo/cromite

[1] https://github.com/ungoogled-software/ungoogled-chromium

[2] https://librewolf.net/

For those that like Chromium but want to remove any integration with Google, there's Ungoogled Chromium

https://github.com/ungoogled-software/ungoogled-chromium

If you're entirely partial to Chromium browsers, use Ungoogled Chrome https://github.com/ungoogled-software/ungoogled-chromium

what about https://github.com/ungoogled-software/ungoogled-chromium