2 ms·
There are tons of forks of the Linux kernel. For example, Debian ships their own, and Ubuntu, which is based on Debian, ships a different one. These are kept mo
by AnthonyMouse 3y ago
There are tons of forks of the Linux kernel. For example, Debian ships their own, and Ubuntu, which is based on Debian, ships a different one. These are kept mostly in sync with upstream but it's completely plausible that if upstream made a change they didn't like they'd just revert it.
The actual problems are with things like systemd, which are enormous and lack standardization but get integrated into numerous parts of the system. Then you can't replace a piece of it or your piece has to integrate with all of the things the original did, but since none of the integrations follow any standards they can change at any time and people can add new ones that only work with the original and -- surprise -- your replacement is suddenly broken.
- margorczynski 3y agoThe thing is most of those changes are minimal and it is completely unrealistic for any non-megacorp to maintain their own implementation of it. The example here would be Google and Android. Another great example is Redis - where the main competing product is now not a fork of the original but a new thing by none other than MS, as they have the cash and resources like Google to pull something like this off.
- AnthonyMouse 3y agoThe general problem here is monorepo disease. Instead of composable components with standard interfaces, you get a single huge project which is too big for anyone to replace as a whole but also has shifting internal interdependencies that prevent you from replacing only a part of it.