Avoid Gecko-based browsers like Firefox as they’re currently much more vulnerable to exploitation and inherently add a huge amount of attack surface. Gecko doesn’t have a WebView implementation (GeckoView is not a WebView implementation), so it has to be used alongside the Chromium-based WebView rather than instead of Chromium, which means having the remote attack surface of two separate browser engines instead of only one. Firefox / Gecko also bypass or cripple a fair bit of the upstream and GrapheneOS hardening work for apps. Worst of all, Firefox does not have internal sandboxing on Android. This is despite the fact that Chromium semantic sandbox layer on Android is implemented via the OS isolatedProcess feature, which is a very easy to use boolean property for app service processes to provide strong isolation with only the ability to communicate with the app running them via the standard service API. Even in the desktop version, Firefox’s sandbox is still substantially weaker (especially on Linux) and lacks full support for isolating sites from each other rather than only containing content as a whole. The sandbox has been gradually improving on the desktop but it isn’t happening for their Android browser yet.
In terms of performance, it’s well known that Blink is faster and it can be tested by just trying both. Firefox stutters and lags while Chromium maintains a smooth framerate.
I disagree with compatibility however. Chromium’s wayland support is iffy and it barely integrates with XDG or VAAPI
GrapheneOS’s objections are irrelevant because you should be using security extensions if you’re old enough to get online without parental supervision. JavaScript has not run on my web browser since Bush Jr was in office. Considering Graphene is made by weirdos who get hysterical if you start asking questions about the difference between admin permissions on a big device that lives on your desk versus a small device that lives in your pocket, they’re pretty firmly relegated to being unserious.
GrapheneOS cites security issues with Firefox.
Citation
In terms of performance, it’s well known that Blink is faster and it can be tested by just trying both. Firefox stutters and lags while Chromium maintains a smooth framerate.
I disagree with compatibility however. Chromium’s wayland support is iffy and it barely integrates with XDG or VAAPI
GrapheneOS’s objections are irrelevant because you should be using security extensions if you’re old enough to get online without parental supervision. JavaScript has not run on my web browser since Bush Jr was in office. Considering Graphene is made by weirdos who get hysterical if you start asking questions about the difference between admin permissions on a big device that lives on your desk versus a small device that lives in your pocket, they’re pretty firmly relegated to being unserious.
Omg this idiot saying no one should use javascript… This is un realistic unpractical and stupid.