Right. I think people were alert to these possibilities long before the actual stuff happened with Manifest V3.
And it shouldn't take waiting until specific examples happen to understand the incentives and the possibilities that could ripen at some future date.
And just to throw in my little side hobby horse on this conversation, it's what I find personally frustrating about conversations with people who think that Brave counts as an alternative.
Being attached at the hip to the Chromium project is a ground level commitment to a long-term vulnerability, and it means that similar circumstances could "ripen" at some future date as the family of Chromium browsers become dependent on an increasingly vast foundation of code and web standards. To me, the combination of that capability and the incentive should be enough to be treated as a complete argument which disqualifies Chromium derived browsers from counting as alternatives.
And it shouldn't take waiting until specific examples happen to understand the incentives and the possibilities that could ripen at some future date.
And just to throw in my little side hobby horse on this conversation, it's what I find personally frustrating about conversations with people who think that Brave counts as an alternative.
Being attached at the hip to the Chromium project is a ground level commitment to a long-term vulnerability, and it means that similar circumstances could "ripen" at some future date as the family of Chromium browsers become dependent on an increasingly vast foundation of code and web standards. To me, the combination of that capability and the incentive should be enough to be treated as a complete argument which disqualifies Chromium derived browsers from counting as alternatives.