I'd hazard a guess that the answer is yes, but we'll see. The thing about Opera (and MS with Edge) is that they've already bitten the give-up bullet once by mov

I'd hazard a guess that the answer is yes, but we'll see. The thing about Opera (and MS with Edge) is that they've already bitten the give-up bullet once by moving to a Chromium-base in the first place, rather than continue with their own separate browsers, so it seems likely to me that if the challenge of maintaining a significant difference is too great they'll bite the bullet again. Somewhat related, I read this about OpenBSD today: https://lwn.net/ml/linux-kernel/19404.1697568901@cvs.openbsd.org/ https://lwn.net/ml/linux-kernel/19404.1697568901@cvs.openbsd... "Robert Nagy in our group maintains 1280 patches to make chrome work on OpenBSD. Google ignores them and will not upstream them. Some of these changes are security related, and they ignore them. Other changes are to cope with security work we've done on our own, for example: JIT changes from Stephen@google for mandatory IBT which google hasn't upstreamed yet, impacts due to PROT_EXEC-only mappings, etc." As far as I can tell, most of these patches (https://cvsweb.openbsd.org/cgi-bin/cvsweb/ports/www/chromium/patches/ https://cvsweb.openbsd.org/cgi-bin/cvsweb/ports/www/chromium...) are just checks for whether the code is on openbsd or not. Still, even in 2019 (https://groups.google.com/a/chromium.org/g/chromium-dev/c/b57hDs8yE4g https://groups.google.com/a/chromium.org/g/chromium-dev/c/b5...) the author made the expected complaint trying to upstream them about how "it is getting really hard to follow all the code moving and new features". Keeping v2 compatibility will predictably get harder and harder over time.