3 ms·

> On iOS, Brave is forked from Firefox You mean the platform that specifically disallows competing browser engines, making Firefox just a shell over a Safari-e

> On iOS, Brave is forked from Firefox You mean the platform that specifically disallows competing browser engines, making Firefox just a shell over a Safari-enabled web view and that can't even access Safari's content blockers? The only Firefox that's not running a Firefox engine under the hood? That Firefox? Given you're a developer for Brave, it's not possible for you to not know this, therefore your statement is misleading at best. The pitfalls of Chromium are obvious... it gives Google the power to impose on the market whatever engine feature they want, they are the ones defining the web standards and there's nothing Brave can do about it because Brave does not have the capacity to maintain a full fork, or to fight for web standards, just like it doesn't have the capacity to build a browser without piggybacking on somebody else. Don't get me wrong, nowadays even Microsoft admitted total defeat, but then Brave should recognize its total dependence on Google and its continued goodwill.

jefftk 7y ago
> Brave should recognize its total dependence on Google and its continued goodwill What do you mean? Brave is based on Chromium, which is open source. Google can't stop people from using it. (Disclosure: I work for Google)
- input_sh 7y ago
  Google is the dictator of what gets accepted into Chromium and what does not. That's how open source development works -- even if the code is available to everyone, its maintainers control its future.
  - ryacko 7y ago
    More significantly, (as far as I know) there is not much open discussion about Chromium’s goals or roadmap. The reduction of Adblock blacklists in Chromium was announced, there wasn’t some public mailing list where a flame war began over it.
  - jefftk 7y ago
    Regardless of how Chromium is run [1] Brave is still in a position to make their browser work however they want. They can choose what Chromium features to enable, and take the code any direction they want. [1] Your categorization doesn't match what I've seen. Microsoft has been driving substantial changes as Edge moves onto it.
bsclifton 7y ago
You're right - all browsers on iOS (as far as I know, including Chrome) are wrappers around Safari. I didn't mean to imply Brave on iOS was based on Gecko, simply that it was originally forked from Firefox on iOS We do have upstream contributions to Chromium. Nowhere near as many as Microsoft (we may only have a few), but we do try to contribute back when possible
csharp 7y ago
(iOS engineer at Brave here) All iOS browsers are based on webkit. WKWebView, which is what we use, does have full access to content blockers. This is how we do ad-blocking, HTTPSE upgrades, and script blocking.

jefftk 7y ago

> Brave should recognize its total dependence on Google and its continued goodwill What do you mean? Brave is based on Chromium, which is open source. Google can't stop people from using it. (Disclosure: I work for Google)

input_sh 7y ago
Google is the dictator of what gets accepted into Chromium and what does not. That's how open source development works -- even if the code is available to everyone, its maintainers control its future.
- ryacko 7y ago
  More significantly, (as far as I know) there is not much open discussion about Chromium’s goals or roadmap. The reduction of Adblock blacklists in Chromium was announced, there wasn’t some public mailing list where a flame war began over it.
- jefftk 7y ago
  Regardless of how Chromium is run [1] Brave is still in a position to make their browser work however they want. They can choose what Chromium features to enable, and take the code any direction they want. [1] Your categorization doesn't match what I've seen. Microsoft has been driving substantial changes as Edge moves onto it.

bsclifton 7y ago

You're right - all browsers on iOS (as far as I know, including Chrome) are wrappers around Safari. I didn't mean to imply Brave on iOS was based on Gecko, simply that it was originally forked from Firefox on iOS We do have upstream contributions to Chromium. Nowhere near as many as Microsoft (we may only have a few), but we do try to contribute back when possible

csharp 7y ago

(iOS engineer at Brave here) All iOS browsers are based on webkit. WKWebView, which is what we use, does have full access to content blockers. This is how we do ad-blocking, HTTPSE upgrades, and script blocking.