I'm guessing it doesn't support certificate revocation very well as ungoogled-chromium has/had some issues with that.

removing every google url in a browser without replacements will have such downsides

> about 3 people are working on it

Hard pass. Arc had an entire dev team with serious investors and couldn't just focus on building a browser

> had an entire dev team with serious investors

thats literally why we get slop, because companies focus on investors rather than users? when there are 3 people working on it, they would listen more to the community

That's because they had serious investors

Touché

Actually it's mostly patch files but they're ignored by github.

it's a few hundred lines worth of scripts to produce an ungoogled chromium with some nicer defaults, why wouldn't it, in case pointing that out is meant to be a criticism.

oh ok, welp, :shrug:

From a few months of use I think qutebrowser is good enough to prove that a python web browser is not inherently a bad idea.

qutebrowser is not technically a "Python web browser". The GUI uses Python Qt bindings, and the browser engine itself is QtWebEngine. Python is simply the glue that ties it all together, and any language could be used instead, since performance is not a concern. This is why there are so many small niche "web browsers", such as Luakit, Nyxt, surf, etc.

Surely performance is even less of a concern for a set of tools applying one time patches to ungoogled chromium?

What about 10,000 ?

Both have their pros and cons, but overall I'd go with the 10,000.

Better than either is the frequency of 3rd party audits/security reviews/research interests - but I think that comes more from usage/popularity than the size of the 1st party dev team.