3 ms·
How open source is a browser if entire other companies can't maintain a fork?
by stavros 2y ago
How open source is a browser if entire other companies can't maintain a fork?
- josephcsible 2y agoOpen-source-ness only depends on the source code being released under a suitable license. It has nothing to do with complexity or maintainability of it.
- JadeNB 2y ago> Open-source-ness only depends on the source code being released under a suitable license. It has nothing to do with complexity or maintainability of it. 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.
- murderfs 2y agoBy that logic, Linux isn't open source. Plenty of companies have abandoned products because maintaining a downstream fork of the kernel is too hard. Companies not being willing to invest resources into maintaining a fork doesn't mean it's not open source.
- Spivak 2y agoBut companies do maintain what are essentially forks of the kernel, both Redhat and Canonical carry their own patches and have ship different kernel variants. It's not politically a fork but it's the same sort of thing.
- JumpCrisscross 2y agoSo whether something is open source depends on whether others bother maintaining it? Even if that doesn’t change that an individual cannot?
- stavros 2y agoYep, exactly. The disagreements here come down to a "spirit vs letter" debate. Yes, Chromium is open source by the letter of the law, as it's licensed under a FOSS license, but FOSS comes with certain expectations that you'll be able to use and modify the source code in certain ways. 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.
- dartos 2y agoWhat’s much harder about maintaining a chrome fork than a fork of the Linux kernel?
- rightbyte 2y agoI don't think the problem is Chrome's source etc, but that Google pulls levers to change the web for the worse by pushing complexity. 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?
- stavros 2y agoOh yeah, definitely, it's not just the codebase. Google is making sure alternate browser engines can't exist by making them much more complicated.
- lxgr 2y agoOpen source and open format/specification/protocol are quite different concerns, and in fact the problem here is with the latter, not the former: 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.
- KetoManx64 2y agoOh hey! Small world! I recently used your Static site generator to convert a subset of my Joplin notes into a website which I used as a showcase for employers and that showcase ended up being the thing that got me my initial interview with the company I'm now working for. Thanks for making the converter public and saving me a bunch of time from not having to write one myself from scratch!
- stavros 2y agoOh nice! I'm really glad that was useful, I use it for myself but I didn't know if anyone else did!
- TheNewsIsHere 2y agoAbsolutely off topic here — what has your experience with Joplin been, if you don’t mind me asking? 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.
- KetoManx64 2y agoI have a bit less notes, about 2700, and the only complaint I have is that the mobile app is a bit sluggish when you open it and it starts to sync, other than that I'm quite content with it. I use it on 6 devices that are a mix of Android/Linux/Windows and my sync is nice and snappy (I use a self hosted Joplin Server as the sync backend). It used to take forever when I used the folder based syncing (with Syncthing for inter device syncing), but with Joplin Server it's MUCH faster. 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.