> while being able to remove anything they don't like, like MV3 limitations on adblockers. … which might actually not be as easy as it sounds. Sure, as long as

> while being able to remove anything they don't like, like MV3 limitations on adblockers. … which might actually not be as easy as it sounds. Sure, as long as Chrome/Blink internally retains MV2 compatibility behind a configuration setting for enterprise customers you job is easy – just hard-code that setting back to enabled for everybody instead of just enterprise users and you're done. However once Google starts ripping out the MV2-related code from the Chrome/Blink code base, all that code suddenly becomes your responsibility to maintain – and from that point on there's always the risk that Google suddenly decides do to some large scale refactoring or internal architectural change that radically conflicts with your attempts to maintain those old features alive. Once you reach that point, you've then got the choice to either spend ever increasing amounts of effort on maintaining those features on top of the current code base, doing a hard fork and therefore having to suddenly maintain the whole shebang, which would be an even larger effort, or instead giving up and dropping those features after all.