Google definitely influences the decision, but they can’t dictate it.
it definitely dictates it when you’re talking about things like APIs exposed etc. no one is going to try and maintain core apis if google isnt going to play nice. sorry you’re just wrong on this one. its played out repeatedly in software for decades. same deal with webkit on apple hardware.
The one who ultimately decides whether to update/rebase to the new version of chromium or not; or abandon chromium entirely and maybe use something else, like Webkit, that many other Linux browsers are using
incorrect. very few browsers will go the extra mile for functionality that google is hostile to. firefox is basically the only one simply because they have their own engine. those that hook into blink almost never do anything more than cosmetic simply because the maintenance burden for doing so is too high.
it definitely dictates it when you’re talking about things like APIs exposed etc.
I gave examples of the opposite in an earlier comment. Though it’s unclear what level of APIs you refer to here, specially given that you said “same deal with webkit” (which, again, is not under google). You might as well apply the same deal to gecko too.
incorrect. very few browsers will […]
This is a contradiction. If few browsers will do it, then my statement that it can happen is correct, and I included that just as one among a list of many other possible choices, including entirely killing their project and contributing to the death of Chromium’s ecosystem, making a scene about it and further sway public opinion towards alternatives… in fact, another option could be to have their team move over to contribute to one of the existing Webkit alternatives, or fork one of those with whichever cosmetic changes their userbase likes. The point was that the final say on what those projects will do is a decision those projects can make, not Google.
it definitely dictates it when you’re talking about things like APIs exposed etc. no one is going to try and maintain core apis if google isnt going to play nice. sorry you’re just wrong on this one. its played out repeatedly in software for decades. same deal with webkit on apple hardware.
incorrect. very few browsers will go the extra mile for functionality that google is hostile to. firefox is basically the only one simply because they have their own engine. those that hook into blink almost never do anything more than cosmetic simply because the maintenance burden for doing so is too high.
I gave examples of the opposite in an earlier comment. Though it’s unclear what level of APIs you refer to here, specially given that you said “same deal with webkit” (which, again, is not under google). You might as well apply the same deal to gecko too.
This is a contradiction. If few browsers will do it, then my statement that it can happen is correct, and I included that just as one among a list of many other possible choices, including entirely killing their project and contributing to the death of Chromium’s ecosystem, making a scene about it and further sway public opinion towards alternatives… in fact, another option could be to have their team move over to contribute to one of the existing Webkit alternatives, or fork one of those with whichever cosmetic changes their userbase likes. The point was that the final say on what those projects will do is a decision those projects can make, not Google.