Fabio Manganiello on Nostr: I also don’t feel very comfortable with [Mozilla’s stance on the ...
I also don’t feel very comfortable with [Mozilla’s stance on the topic](https://blog.mozilla.org/addons/2024/03/13/manifest-v3-manifest-v2-march-2024-update/ ) either:
> *“Firefox, however, has no plans to deprecate MV2 and will continue to support MV2 extensions for the foreseeable future. And even if we re-evaluate this decision at some point down the road, we anticipate providing a notice of at least 12 months for developers to adjust accordingly and not feel rushed.”*
I really don’t like that “*even if we re-evaluate … 12 months notice…*“ part. I know that the folks at Mozilla may have the best intentions, but with all Chromium-based browsers leaving V2 behind Mozilla will basically become the sole maintainer of the old Manifest API. Brave at some point announced that they’ll keep supporting it as well, but 1. I don’t trust anything that comes out of Brendan Eich’s mouth, and 2. if they decide to keep supporting V2 then they’ll basically have to maintain their own fork of Chromium that keeps the old API.
I feel like Google used its weight played the long game quite well here. Of course we all know why V3 came out. Of course nobody likes it. But hey, what are you going to do? Maintain your own fork of V2 without having even a fraction of Google’s resources, and while serving ~5% of the market? Hmm…
> *“Firefox, however, has no plans to deprecate MV2 and will continue to support MV2 extensions for the foreseeable future. And even if we re-evaluate this decision at some point down the road, we anticipate providing a notice of at least 12 months for developers to adjust accordingly and not feel rushed.”*
I really don’t like that “*even if we re-evaluate … 12 months notice…*“ part. I know that the folks at Mozilla may have the best intentions, but with all Chromium-based browsers leaving V2 behind Mozilla will basically become the sole maintainer of the old Manifest API. Brave at some point announced that they’ll keep supporting it as well, but 1. I don’t trust anything that comes out of Brendan Eich’s mouth, and 2. if they decide to keep supporting V2 then they’ll basically have to maintain their own fork of Chromium that keeps the old API.
I feel like Google used its weight played the long game quite well here. Of course we all know why V3 came out. Of course nobody likes it. But hey, what are you going to do? Maintain your own fork of V2 without having even a fraction of Google’s resources, and while serving ~5% of the market? Hmm…