Once Google rips the MV2 code out of Chromium entirely next year, are Opera's developers really going to have the resources necessary to maintain such a hard fork?
Somewhat related, I read this about OpenBSD today: 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...) 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/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.
Worst comes to worst they can use the Firefox engine. The MV2 extensions don't need much work to leap over for Firefox
I wish that was the outcome. I could finally try firefox with a ui that fits my workflow.
That's a definition, but I think that stavros was proposing that, much like Microsoft's "open" formats for Office, if a codebase is so complex that no-one else, not even with the resources of a full company, can maintain it, then at best its open sourceness is pro forma.
Companies not being willing to invest resources into maintaining a fork doesn't mean it's not open source.
The fact that Google has managed to make a codebase open, but extremely onerous to actually maintain a fork of, does actually go against the spirit of FOSS a bit, in my opinion.
It becomes an ever going churn to keep up.
I haven't read the Chrome source but is it any worse than say Linux or gcc?
The modern web stack is so complicated that any current browser engine has a significant moat.
In other words, the problem isn't that Chrome is not open source; the problem is the amount of work it takes to maintain or compete with it.
I recently tried to migrate to Joplin from an amalgamation of notes apps (including Standard Notes, via an ENEX converter in between). I really wanted to love it, but it proved to be unusably slow. I think it might have been my WebDAV service, but replacing it wasn’t a project I was interested in. That was with about 3,000 notes, so I’m not sure if my experience is typical.
Do you have OCR enabled for your images within Joplin settings? I tried that a while back on a work instance and it REALLY slowed things down. I've been hesitant about enabling it on my home instance.