1–10 of 191 posts
I’m wondering if that are technical reasons why the newish browsers (such as Brave or Edge) are choosing Chromium instead of Firefox as their starting point.
If so, shouldn’t this be a priority for Mozilla to change that?
Quoted post unavailable.
If you think that there are engineers specifically on the Chrome/Chromium team who ARE interested in the technology, what's the chances that there are engineers on the Firefox team who feel the same?
My point being companies will always have to be monetarily-biased, and the hope is that the team working on the product itself still believe in it because they don't get much kickback from management's decisions about the technology.
Quoted post unavailable.
And you're saying Google's isn't the same? Mozilla and Google are both businesses whose primary goals are obtaining money. If you think that there are engineers specifically on the Chrome/Chromium team who ARE interested in the technology, what's the chances that there are engineers on the Firefox team who feel the same? My point being companies will always have to be monetarily-biased, and the hope is that the team…
Chrome is easy to fork, Firefox is not. It's pretty much that simple.
Servo isn't a finished rendering engine yet and the browser I saw that could exclusively use servo was not compliant enough and since mozilla fired the servo team there is no certain future for it anymore. Projects that tried to make servo embeddable are all dead and gone (see https://github.com/paulrouget/servo-embedding-example for example)
So yeah last time I tried to use gecko I failed and didn't try again (years ago) nobody is willing to do the work and mozilla seems to focus more on other stuff...
Even spidermonkey, the javascript engine, is never reused as v8.
Different design priciples
Other than Ekioh’s Flow, I don’t know any other competitive attempts from companies building browser components from scratch.