51–60 of 191 posts
Security. The world class team that is responsible for protecting the iPhone protects Chromium.
Are you talking about Google's Project Zero? If so, you can include lots of software with that logic, and it would make even less sense to say that "the world class team that is responsible for protecting Intel processors protects Chromium".
I'm wondering, Tor [1] is a Firefox based browser in the same sense as Edge/Brave/+ are based on Chromium? [1] https://www.torproject.org
Wasn’t chromium based in WebKit? Same as Safari. Basically Apple forket webkit to make safari and Google forked WebKit to make chromium. I really don’t see what the hubbub is about trying so hard to have gecko, webkit, etc. rendering engines out there. If the end goal is standards compliance, the outcome should be the same. The fact that Google did such a good job on early chrome compared to everyone else is really w…
Earlier quoted context omitted.
But aren’t Brave, Edge and Opera based on Chromium instead of only Blink? Am I missing something?
Blink is a part of Chromium, but not really a decoupled part. Having blink without the rest of Chromium isn't really possible at this time. Some details at https://www.chromium.org/blink https://www.chromium.org/developers/content-module
But the "embedding gecko is hard, embedding chromium is easy" explanation certainly seems to be wrong, in terminology at least.
Out of the blue yesterday my phone asked me to rate Firefox. I think Google is trying to create a facade of competition where there is none by stuffing the Play Store review stats.
Earlier quoted context omitted.
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…
Technically Mozilla is non-profit and thus technically not in the business of obtaining money.
It has this weird structure because the search deal makes too much money relative to donations according to IRS nonprofit rules.
If B corps existed back when this structure was created, then they would have incorporated as that, but B corps didn’t exist then, and there’s no benefit to reincorporating as a B corp now.
That was Apple's reported reason for using KHTML and making WebKit which Google used for Chrome and forked eventually. They wanted something light and embeddable. Don't blame them. Also, that software was LGPL.
I was always hoping that Microsoft or Apple would fund the Mozilla Foundation to keep a competitive web engine afloat and prevent Google Chrome engineers from dominating the web. They can take the Firefox code for their closed source software under the MPL.
Really doubt MS is going to do that these days. Kinda hoping Apple does since Safari is often the last to support new web standards. It would take very little of their profit and yet keep a big competitor from dominating a critical function of their most profitable products. This is regardless if they actually use Gecko or Servo.
Otherwise firefox is a slower, less secure browser and an older more crufty codebase and less webdevs test it thoroughly. Why would I choose it as a new browser wrapper developer ever?
It seems like everyone has reached much the same conclusion: there may be many factors, but the real killer and root cause is that Chromium is well suited to being embedded, and Gecko is not. So hey, any companies out there interested in bringing back a little diversity in browser engines? Or just making a tiny dent in Google's dominance for the greater good? Consider funding work to make Gecko better suited to embed…
It seems like everyone has reached much the same conclusion: there may be many factors, but the real killer and root cause is that Chromium is well suited to being embedded, and Gecko is not. So hey, any companies out there interested in bringing back a little diversity in browser engines? Or just making a tiny dent in Google's dominance for the greater good? Consider funding work to make Gecko better suited to embed…