2 ms·
> Linux (the larger operating system environment) exists only because of its monolithic approach to kernel-space development. Far from suffering from it, it mad
by lmm 8y ago
> Linux (the larger operating system environment) exists only because of its monolithic approach to kernel-space development. Far from suffering from it, it made it all possible when the utopia of the GNU kernel flat-lined.
Linux-the-kernel was largely just in the right place at the right time, but to the extent that it had development advantages they were an openness to contributions and the absence of an imposed top-down design.
> Open source has succeeded because it was easy to improve and replace things piecemeal. But deciding that the individual pieces must begin and end at the process level is blinkered. You can perform "piecemeal improvements" to the scheduling component in systemd just as easily as you can to, say, cron.
You can submit changes and improvements to a given cron implementation. But if there's a really hard tradeoff or a disagreement, you can also fork off your own cron implementation, and in fact there are three or four different cron implementations in common use on linux. This is really important and not just in the cases where a fork actually occurs: the possibility of a fork encourages maintainers to be reasonable and come to a consensus.
Systemd's tightly coupled design makes that impossible - it's not about process boundaries but about having any kind of boundary where there's a stable interface between different components. E.g. reasonable people can disagree over whether the advantages of a binary logging format outweigh the disadvantages. But the systemd maintainers have taken a particular position, and, crucially, people who disagree can't just fork the logging component and swap it out for their piece, because there's no stable interface between that and the rest of the system.
- sjwright 8y agoNone of that makes any sense to me. It's all open source. Suggesting that you can fork cron and you can't fork systemd is patently absurd. You say that "people who disagree can't just fork the logging component and swap it out for their piece" when in reality you really can. Getting systemd to output text logs is trivial, just point it to syslogd instead of journalctl. It sounds like you weren't aware of that. So much for being a tightly coupled design.
- sjwright 8y agoYou say the Linux kernel had an "absence of an imposed top-down design"? Ha. Haha. Am I supposed to take that seriously? The Linux kernel wasn't a top-down design? Do you remember the Linux kernel? Do you know who Linus Torvalds is?