Yeah... relying on Chromium and "don't be evil" Google definitely sounds like fun.
It's sad that Firefox engine is so difficult to embed and we could have seen more projects using it.
It's sad that Firefox engine is so difficult to embed and we could have seen more projects using it.
Possibly Google paying companies to bundle Chrome with their software installers had a part as well.
Perhaps putting a Chrome advertisement to the Google homepage and recommending an "upgrade" to all Google visitors played a part too. Maybe.
* A safer browser. * A more performant browser.
Which was more than enough for most of us to recommend everyone switch. Much the same was as when Firefox first came out it was unambiguously:
* A safer browser. * A more performant browser.
Which was more than enough for most of us to recommend everyone switch. The switching cost of a browser is quite low. The next browser to meet the above criteria will experience a similar jump in users. The challenge is in actually delivering a browser that can do so. The web standards are massively complex for many reasons, some of them legitimate. The barrier for entry is going up over time and shows no sign of slowing down.
Remember, Chrome was released in 2008. Internet Explorer, with almost 2/3 of the browser marketshare, was on version 7 at that time and a stupid number of corporate IT departments would continue to default to IE 6 rather than updating or fixing their ancient garbage applications for years to come.
Chrome provided a way for power users to have a non-shitty browser, which then blossomed from there as more and more web sites made use of modern browser capabilities and worked worse and worse in corporate-mandated IE instances.
Putting on my BOFH hat obviously I'm not the biggest fan of such "shadow IT" processes but I understand that they happen when needs and wants aren't being met and sometimes this is the most effective way to force a necessary change.
Mozilla has made some bad decisions but we should acknowledge that a fair fraction of them were also flailing around trying to recover from those competitors’ actions. I don’t think Firefox OS would have happened if, for example, iOS allowed a real browser market.
I can confirm that Google didn't wasn't testing on Firefox first as of the early-to-mid 2010s, but that was an efficiency-of-testing decision; how much should a company spend on testing a browser with a sub-10% market share?
... That sounds like it's on Mozilla.
Its deprecated
There are two types of deprecated APIs: ones nobody uses and ones everybody uses. Sounds like Mozilla mis-guessed on which one of those Shadow Dom v0 would be.
(From my limited experience: I bet while the Chrome team was trying to deprecate shadow dom v0, YouTube, which still operates as a pretty independent arm inside the Google ecosystem, built a new system on Polymer and in terms of Google's management architecture, nobody has authority to tell them not to do that. Far from an intentional shafting of other browsers, it was likely a failure to coordinate internally coupled with total apathy regarding what that meant for other browsers, since from YouTube's point of view, Chrome is free and available to everyone.
Never attribute to malice that which can be explained by disorganized-bag-of-cats management style).
And, despite it being google - they don’t force me into the options menu to remove advertising off of my Home Screen, and have never forcibly installed extensions advertising TV shows.
There are as many project using Gecko as they are using WebKit (roughly). [1]
Browser framework that Firefox is built on is called Quantum. Other Quantum browsers are LibreWolf, Tor, Pale Moon etc..
Chrome and clones are based on Chromium.
Interestingly there is no browser framework available for WebKit rendering engine and every WebKit browser has to be built from scratch on top of WebKit.
Web rendering engine -> Browser framework -> Browser
Blink -> Chromium -> Chrome, Edge, ...
Gecko -> Quantum -> Firefox, LibreWolf, ...
WebKit -> -> Safari, Orion, ...
[1] https://twitter.com/vladquant/status/1492181669788356611/pho...
The interface looks exactly the same.
If you look for "embedding Gecko", all the documentation seems to be archived/deprecated. It doesn't seem to be supported by Mozilla anymore. And it was never easy.
Not on Android, it isn't. https://geckoview.dev