I was answering forking and how realistic it is. You’re changing the conversation into specifics around chrome.
I’m not changing anything. they are powerless. if google decides to change chrome for the worse in a more significant way than UI design, they cannot avoid accepting that change.
if you meant Mv2, I doubt they will be able to keep up with the support for long. for now it’s very easy, because all the code is still there in the engine (recently you could still reenable it even in google chrome), but once chromium starts to refactor code, to make it simpler or more modern, those changes will not be done with kerping Mv2 support in mind, and fork devs will have an increasingly harder time to patch back support for it (safely!) as time goes on.
I’m not changing anything. they are powerless. if google decides to change chrome for the worse in a more significant way than UI design, they cannot avoid accepting that change.
Your example was Mv3. There are plenty of Chromium browsers that still support Mv3. What’s your point?
all up to date chromium browsers support Mv3.
if you meant Mv2, I doubt they will be able to keep up with the support for long. for now it’s very easy, because all the code is still there in the engine (recently you could still reenable it even in google chrome), but once chromium starts to refactor code, to make it simpler or more modern, those changes will not be done with kerping Mv2 support in mind, and fork devs will have an increasingly harder time to patch back support for it (safely!) as time goes on.
Sure thing bud.
Now back to the actual topic…