4 ms·
The linux codebase exists in stark contrast to your claim. Assuming your claim is that broken up repos is the better way.
by taeric 9y ago
The linux codebase exists in stark contrast to your claim. Assuming your claim is that broken up repos is the better way.
- hueving 9y agoNo it doesn't. I think you are thinking of the kernel, which is separate from all the distros. Linux by itself is just a kernel and won't do anything for you without the rest of the bits that make up an operating system.
- taeric 9y agoThen I'll point to the wide success of monolithic utilities such as systemd as evidence that consolidating typically helps long term. Which is to say, not shockingly, it is typically a tradeoff debate where there is no toggle between good and bad. Just a curve that constantly jumps back and forth between good and bad based on many many variables.
- hueving 9y agosystemd is also completely useless on its own. It still needs a bootloader, a kernel, and user-space programs to run. When it comes to process managers, there is obviously disagreement about how complex they should be, but systemd is still a system to manage and collect info about processes.
- caf 9y agoThe hierarchical merging workflow used by the Linux kernel does mean that there's more friction for wide-ranging, across-the-whole-tree changes than changes isolated to one subsystem.
- taeric 9y agoIsolated changes will always be easier than cross cutting ones. The question really comes down to whether or not you have successfully removed cross cutting changes. If you have, then more isolation almost certainly helps. If you were wrong, and you have a cross cutting change you want to push, excessive isolation (with repos, build systems, languages, whatever), adds to the work. Which typically increases the odds of failure.