Today's new desktop browser replaces the Muon-based version on our site. Users who now browse with the Muon version (0.25.2) will get Muon updates until they are fully upgraded to this new version in the near future. They can also download the new version:https://brave.com/download/
-
-
We had few people, fewer C++ hackers, and relatively lots of UX to do. Seed 1 funding was small, chromium FE needs more than a few hands (e.g., just to neuter all the requests to Google servers), the Gecko-based version had HTML UX, so...
-
OK. I don't know how Electron addresses those issues but I don't doubt that it did something to make it less work to get started.
-
VS Code, Slack, Atom, Signal Desktop, many others use Electron. It is catnip to web devs who know Node.js. We had to turn on chromium sandboxing in a hurry, then fork harder to fix other security bugs. But as noted it's absolutely easier than alternatives to knock out lots of UX.
-
Is the 22% performance win in latest Brave browser due to eliminating fundamental overheads imposed by Electron/Muon? Or is it because direct Chromium embedding let's you use a newer & faster Chromium version?
-
We keep up with chromium stable in all products so cr version will not differ comparing stable to stable. But now that you mention it, https://brave.com/new-brave-22-percent-faster/ … should’ve been explicit about chromium version for Brave 0.24.0 (cr 69) vs brave-core 0.55.12 beta. Cc:
@convoluted_code. -
Thank you for the article update. It is now explicit. "Brave 0.24.0 is based on Chromium build 69.0.3497.100, while Brave Core 0.55.12 uses a newer Chromium build 70.0.3538.45" Not a big delta, so I remain curious on the cause of the 22% perf win.
-
Rob, we measured Chrome 69 vs Chrome 70 -- the difference on most site is very small, a few percentage points, the median under normal laptop coniditions is Chrome 70 being 2% *slower*. So, it seems that the new Brave architecture is the main source of the perf improvement.
- 2 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.