I don’t think so. Mozilla looked at using Blink/Electron a few years ago, but decided to all in on Gecko, Rust, etc. instead. Although engine is important, it’s not the limiting factor here.
-
-
Replying to @marcosc
I'm not suggesting Gecko is the limiting factor, just that keeping it competitive with Chromium at the platform level is guzzling resources which could be used to innovate in areas closer to Mozilla's mission (and more impactful).
2 replies 0 retweets 5 likes -
I’m joining late, I know. I think the framing is wrong here. Chrome, and through the lack of protections also Blink, are becoming the example of what *not* to do with the web platform. Hopefully, they’ll change but joining that project now is the opposite of being progressive.
2 replies 0 retweets 11 likes -
Replying to @johnwilander @marcosc
I understand those considerations, but it seems Edge is able to add privacy-protecting mechanisms on top of Blink/Chromium, no? Or am I missing pieces.
1 reply 0 retweets 2 likes -
We’ve been doing it a lot longer at
@Brave — it is adversarial, even ignoring intentions, because chromium is big and hard to audit and rearchitect incrementally downstream, while upstream adds features that may weaken or subvert privacy.2 replies 1 retweet 14 likes -
Replying to @BrendanEich @johnwilander and
Well, precisely. Wouldn’t bringing Mozilla’s strong, privacy-orientated engineering culture to Chromium potentially help with this, not only for Firefox users but for users across the board?
3 replies 0 retweets 1 like -
Replying to @tobie @BrendanEich and
I think that what
@brave is doing is what you are suggesting, and@BrendanEich is testifying that the relationship is adversarial. I think you're deeply discounting the power of controlling your own implementation. Remember the original Blink fork?3 replies 0 retweets 11 likes -
I don't think that what Brave is doing is what Tobie suggested though. He talked of taking Chromium to an open governance model, evidently this would have to remove it from Google, not to involve working downstream.
3 replies 0 retweets 4 likes -
Replying to @robinberjon @tobie and
What leverage does Mozilla have to force Google to relinquish more control over Chromium?
2 replies 0 retweets 0 likes -
Replying to @wycats @robinberjon and
I've been hesitant to wade into this whole topic but I think it's fascinating how the conversation has shifted from "Mozilla should adopt Blink" (few years ago) to "Mozilla should adopt Blink *if* Chromium changes its governance" (today).
2 replies 0 retweets 8 likes
(to be clear, I think the latter is so extraordinarily unlikely to happen that it's not even worth discussing)
-
-
Replying to @pcwalton @robinberjon and
Yes, this is so evident to me that I'm feeling a bit of vertigo that it's even something we're discussing. I could imagine some technical governance changes, but nothing that would substantially relinquish Google control.
2 replies 0 retweets 5 likes -
Interesting. I feel like it could have a ton of benefits for Google. Also the risk is actually very limited: if it doesn’t work out, you fork and you’re back with the current status quo, and potentially even with a good story if you spin it properly.
1 reply 0 retweets 0 likes - 11 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.