[erikrothoff]

As someone working on a massive migration from MV2 to MV3 (where the benefit to the user will be minimal) it does feel like browser makers are waging war against us extension developers. Mozilla's plan is to release a slightly compatible API, but not at all compatible, and yet highly limit what can be done? Do they really think this will increase the effort invested in their ecosystem?

[joecool1029]

I think ultimately the biggest question people need to ask is: Is it more important for Mozilla to fall in line behind Chromium and track compatibility with their ecosystem or is it better for them to support their own extension ecosystem and not make busy work for extension developers?

Can they maintain MV2 while supporting MV3 their own way for easier porting of Chromium extensions? Or is MV2 support getting dropped and all MV2 extensions have a EOL coming up next year?

[Daedren]

I don't think Mozilla has a choice here. Chrome just has the sheer market power at the moment. If Mozilla went down a different path, extension developers would likely just favor Chrome (and MV3) as that's where unfortunately most users are.

Even if they provided an easier path to MV3, developers would likely have hurried up anyway because Chrome won't do so.