I wish someone could explain to me how it is firefox, which is not chromium based but larely dependent on google for funding, has the ability and manpower to maintain not just the manifest v2+all the other stuff, while every single chromium fork has no choice but to use v3. Why can’t they just fork the last usable version of chromium and go from there as an independent fork? Is it just that no one wants to?
Like firefox has lots of ports, some of the follow the main branch but then others like waterfox forked off older versions at some point and just kept going, why can’t chrome based browsers do a fork like that? How is it there are people making new browsers from scratch like ladybird, but this manifest stuff is just out of reach for everyone, except mozilla (and i guess other firefox forks).
Developing a browser, Firefox or Chrome, takes a huge amount of effort, and are on a similar scale to both Windows and Linux. It’s a lot. There are a lot of places to hide things. Taking all of that, and making V2 continue to work… well it’ll be alright to start with. It’s probably a flag somewhere currently. But in 2 years time? 5 years time? It will take a lot to keep V2 working, let alone back porting V3 features that people may actually want.
But firefox is funded by google and has been making questionable decisions for years, LibreWolf is the only fork I would use at this point but I think waterfox really proves my point though that its not really the impossible undertaking people seem to be making it out to be. Waterfox even support BOTH chrome and firefox addons somehow and they have no where near the amount of funding or manpower Mozilla does.
No LibreWolf IS the only fork of Firefox I’ll use (meaning i dont use mozilla’s branded firefox). Although I guess there is one other firefox fork i use now that i think about it: Tor Browser.
I also use Vivaldi, which doesn’t depend on Google for funding and has its own built in adblock that isn’t based on either manifest version. In terms of UI vivaldi is completly unmatched, There’s a japanese firefox fork that attempts to copy it, but its nowhere near as good.
Not having control of the core codebase, and branching/tracking based on 1 (declared) legacy feature could lead to huge amounts of work and issue in the future.
Manifest V2 spec is defined, manifest V3 spec is defined… They can be developed against.
JS-whatever-spec is defined, CSS-whatever-spec is defined, HTML-whatever-spec is defined… They have industry standard approved specs (even if they can be vague in areas). They can be developed against.
They have defined spec documents that can be developed against.
Firefox has control and experience of how they implement those specs.
Chrome forks do not have control of how those specs are implemented.
So if chrome changes how things are implemented, forks might not be able to “backport” for manifest V2 compatibility, and might find themselves implementing more and more of the core browser functionality. Browsers are NOT easy to develop for the modern fuckery of the web.
Firefox hopefully does have that knowledge and ability to include V2 manifest backwards compatibility in future development without impacting further spec implementations… It seems like Google is depreciating V2 to combat ad-blockers (ads being their major funding revenue)
There are already very slight differences how Firefox and Chrome interpret all these specs. I’ve noticed a few sites & plugins that just work better (or just work) in Chrome. Which is why I still have (unfortunately) an install of Chrome.
I wish someone could explain to me how it is firefox, which is not chromium based but larely dependent on google for funding, has the ability and manpower to maintain not just the manifest v2+all the other stuff, while every single chromium fork has no choice but to use v3. Why can’t they just fork the last usable version of chromium and go from there as an independent fork? Is it just that no one wants to?
Like firefox has lots of ports, some of the follow the main branch but then others like waterfox forked off older versions at some point and just kept going, why can’t chrome based browsers do a fork like that? How is it there are people making new browsers from scratch like ladybird, but this manifest stuff is just out of reach for everyone, except mozilla (and i guess other firefox forks).
A port of a browser is relatively minimal effort. Typically, the changes are largely cosmetic, and occasionally skin deep.
There’s a reason none of the ports of Chrome caught the recent snafu with Google having its own special addon that fucks your privacy.
Developing a browser, Firefox or Chrome, takes a huge amount of effort, and are on a similar scale to both Windows and Linux. It’s a lot. There are a lot of places to hide things. Taking all of that, and making V2 continue to work… well it’ll be alright to start with. It’s probably a flag somewhere currently. But in 2 years time? 5 years time? It will take a lot to keep V2 working, let alone back porting V3 features that people may actually want.
Just use Firefox instead.
But firefox is funded by google and has been making questionable decisions for years, LibreWolf is the only fork I would use at this point but I think waterfox really proves my point though that its not really the impossible undertaking people seem to be making it out to be. Waterfox even support BOTH chrome and firefox addons somehow and they have no where near the amount of funding or manpower Mozilla does.
Removed by mod
No LibreWolf IS the only fork of Firefox I’ll use (meaning i dont use mozilla’s branded firefox). Although I guess there is one other firefox fork i use now that i think about it: Tor Browser.
I also use Vivaldi, which doesn’t depend on Google for funding and has its own built in adblock that isn’t based on either manifest version. In terms of UI vivaldi is completly unmatched, There’s a japanese firefox fork that attempts to copy it, but its nowhere near as good.
Not having control of the core codebase, and branching/tracking based on 1 (declared) legacy feature could lead to huge amounts of work and issue in the future.
Manifest V2 spec is defined, manifest V3 spec is defined… They can be developed against.
JS-whatever-spec is defined, CSS-whatever-spec is defined, HTML-whatever-spec is defined… They have industry standard approved specs (even if they can be vague in areas). They can be developed against.
They have defined spec documents that can be developed against.
Firefox has control and experience of how they implement those specs.
Chrome forks do not have control of how those specs are implemented.
So if chrome changes how things are implemented, forks might not be able to “backport” for manifest V2 compatibility, and might find themselves implementing more and more of the core browser functionality. Browsers are NOT easy to develop for the modern fuckery of the web.
Firefox hopefully does have that knowledge and ability to include V2 manifest backwards compatibility in future development without impacting further spec implementations… It seems like Google is depreciating V2 to combat ad-blockers (ads being their major funding revenue)
There are already very slight differences how Firefox and Chrome interpret all these specs. I’ve noticed a few sites & plugins that just work better (or just work) in Chrome. Which is why I still have (unfortunately) an install of Chrome.
You could also just stop using sites that don’t work in Firefox. Also https://webcompat.com/
Absolutely.
And casually, that’s exactly what I do. To be honest, casually I haven’t encountered any (I don’t think…).
But for work stuff, sometimes I don’t have a choice. I guess I’m just thankful it doesn’t require edge IE compat mode, or even IE itself
waterfox ftw