Perhaps this is no longer an option for you but I just wanted to get a broader idea of Brave’s current Chromium based engine and whether you’re obligated now to use that engine indefinitely over newer technologies. I also wanted to ascertain any issue’s it may bring and possibly discuss with a couple of members about any implications that would prevent you from adopting Mozilla’s new Quantum engine and newer technologies/languages for that matter.
It’s widely understood that newer technologies and languages are being optimized to enhance software and not to annoy you because you’re already obviously aware of this, but Apple’s change to Swift and its switch to use the language across its products and Google’s new Fuchsia optimizing rather ironically Mozilla’s Rust language and Mozilla using the language in it’s soon to release Quantum engine seems an indication that greater performance and efficiency lies with Mozilla’s technology. Furthermore, I remember distinctly that we/the community once got into a discussion of the reason as to why you chose the Chromium engine over Mozilla’s almost deprecated older Gecko engine and your description of the issue was reasonable and you clearly stipulated that it wasn’t entirely Google’s engine that you were optimizing to deflect some users concerns around privacy and that you investigated it thoroughly and the results were clear. Chromium it was to be.
That being said, given the great enhancements made to Mozilla’s new Quantum engine, will you be implementing it, or is this not an option any more?
Assuming it was an option, could your fork of Electron (Moun) operate with Mozilla’s new engine without any major rewrites, essentially making an easy/flexible possibility?
This again is in reference to 1.0’s major goal of ‘Make this the best browser for quality and performance imaginable’.
A for argument to implement Quantum apart from it’s performance - I imagine if this was an option, your implementation of the Tor Private Browsing (TPB) feature may be more easy. I state this because, I read on Github where someone explains the challenges that Chromium poses to properly implementing TPB because of the nature Chromium. (I’ll post the link if a reply is made surrounding this issue, otherwise I want waste your time any further)
Thanks for reading.