Many of the Chromium forks have small teams, sigificantly smaller and with little actual in-engine experience compared to Firefox for example.
These teams need to have sufficient resources to maintain a reasonably significant fork of a standard, which will likely get harder over time, and which none of them presently deal with, as they ride the standards implemented by Chromium so far.
Additionally they would have to maintain their own extension stores, which many presently don’t.
Well, there are always different ways for devs to choose. Right now users want mv2 extensions, but later they could switch to mv3, so devs could decide to drop mv2 support.
I agree with extensions store, if google removes mv2 extensions from their store that will make harder to install them, it will also would be not good for devs probably, so eventually mv3 will take place… Or Firefox could be a place where all mv2 are now…?
It is much more difficult than that imo.
Many of the Chromium forks have small teams, sigificantly smaller and with little actual in-engine experience compared to Firefox for example.
These teams need to have sufficient resources to maintain a reasonably significant fork of a standard, which will likely get harder over time, and which none of them presently deal with, as they ride the standards implemented by Chromium so far.
Additionally they would have to maintain their own extension stores, which many presently don’t.
Well, there are always different ways for devs to choose. Right now users want mv2 extensions, but later they could switch to mv3, so devs could decide to drop mv2 support.
I agree with extensions store, if google removes mv2 extensions from their store that will make harder to install them, it will also would be not good for devs probably, so eventually mv3 will take place… Or Firefox could be a place where all mv2 are now…?