3 ms·
That's not the problem. [good] Keep it simple. [why Plan9 mk?] Stable release model with binary packages and a ports system (Plan9 mk-based). [why static lin
by glibgil 11y ago
That's not the problem.
[good] Keep it simple.
[why Plan9 mk?] Stable release model with binary packages and a ports system (Plan9 mk-based).
[why static link? Why musl-libc?] Statically linked, using musl-libc.
[never heard of them. Explain] Sane simple base utilities, see: sbase, ubase, hbase etc.
[hmm... I think I get it] Package management using mount overlays (aufs), but mostly FHS compatible.
[fine] UTF-8 locale.
[good, popular enough to not need explanation] libressl linked.
[what's that?] No Native Language Support (NLS).
[what instead?] No systemd and rabbit hole.
[fine] No binary blob drivers (except linux-firmware).
[perfect example of explaining with just the right amount of detail] Separate /emul namespace for legacy or binary-blob software (skype, wine, robot-unicorn-attack).
- vezzy-fnord 11y agonever heard of them. Explain Their URLs lead to their respective cgit repos, where looking at the top-level source tree immediately demystifies their purpose. Rest is nitpicking by some nebulous standard that barely any project satisfies. It's clearly mentioned that sinit and svc replace systemd, too.