(no title)
waweic | 4 years ago
This is only due to the failure (and unwillingness) of Mozilla to build a truly modular, expandable browser.
Mozilla isn't even trying to compete with Google anymore at this point. They are only implementing new features into Firefox that Google has first built into Chrome (and firing developers working on features that could actually set Firefox apart from Chrome). Also, they are quick to implement most "features" Google implements, no matter how user-unfriendly it may be.
An example for this is Mozilla implementing Manifest V3:
https://www.eff.org/deeplinks/2021/11/manifest-v3-open-web-p...
gruez|4 years ago
>An example for this is Mozilla implementing Manifest V3:
I fail to see how "implementing manifest v3" is user-unfriendly. I can see how people think that way, because "implementing manifest v3" is being conflated with "removing blocking webRequest API". However, there really isn't any indication that mozilla is doing the latter. For instance, you could implement manifest v3 but still supporting v2, or drop v2 but still keep the blocking webRequest API as a vendor specific API. There are good reasons to do the former, to allow firefox to work with extensions built for chrome, so I don't see any issues with mozilla implementing v3.
heresaPizza|4 years ago
8K832d7tNmiQ|4 years ago
They used to have one, but just largely forgotten and abandoned.
dblohm7|4 years ago
Not on Android: https://geckoview.dev
mariusor|4 years ago