Systemd free distro

antiX for shit computers with no RAM.

MXlinux for the rest.

tried these both once. both were equally shitty.

That's a shame, but ideally the main drive(s) should be backed up regardless of the filesystem setup, not that I'm taking my own advice right now. I gotta get around to that someday...
Its worth noting that Btrfs is most stable on the stable kernel series, 5.1.x, and with the latest stable version of btrfs-progs. They've made some good progress there so far, hopefully within the next few years Btrfs will shake off its terrible reputation and become more stable.

gentoo eat crap:
Gentoo + compiled kernel + apps + no X + own flags = 100 MB RAM
default flags = 150 MB RAM

slackware binaries = 64 MB RAM

fuck you gentoo

Well, for starters, how many versions of the same package are you gonna get? 2? 3? 15? How many of them are going to have dependencies and dependants different from the "main tree"? See where I'm getting at? It's a nightmare. On a tangential note, how many storage are you gonna use?
You have posted some awful dependency graph yourself. Now imagine how much more it complicates when you add a fuckton of versions on top of it.
And ALL of these dependencies are gonna be maintained manually by you. I mean, sure, the PM will handle this shit for you "once the packages are written", but somebody gotta write them first LMAO. In case of your customizations, this is gonna be you, and you alone.
The outside repos are only good if they work for you. Same goes for the main repo, if course.

Got me here, I am a vi appreciator and a don't like LISP and functional paradigm in general. The only good thing coming out of FP is pure functions - fucking fight me on that, I dare you.
Why cannot it be declarative brain-dead little-to-no-syntax-encumbered code? Is there any reason to use this parentheses shit? Fuck y'all. Gentoo ebuilds are hardly better, I admit, but better still.
I get that it is undermaintained garbage and you know what? If I have knowledge and time to do that much of work, why wouldn't I just start my own one-person distro with my own PM and stuff, hmm? Tell me one fucking reason, just one.
I get that it is a powerful abstraction and potential of managing source-based Linux ecosystem here is actually immense. The problem comes from a) broken shit because of undermaintainage issues and b) general overengineering of your distro when you have your "immutable storage" all over the place.
Like, just thinking about maintaining this shit makes my head spin. Is it everything you do with your life, maintaining Linux distros? Get outta here.
And BTW, immutability idea is fucking garbage. Pure FP findmaxelem() algorithm will take O(N^2) data as it will allocate N, then N-1, N-2 etc shit recursively. CAN YOU BELIEVE THIS SHIT?
WHAT IS THE FUCKING POINT OF THIS WHOLE PARADIGM THEN YOU FUCKING PIECE OF SHIT SOYBOYS? ARE YOU FUCKING KIDDING ME? JUST WRITE IMPERATIVE CODE WITH NO SIDE-EFFECTS THEN YOU MOTHERFUCKERS.
God I hate you all.

You never know - imagine you're using a system shared between many users - they could have many versions of the same program and Guix prevents the system from being messy. And just two programs using the same library can be a problem.
That's the graph showing dependencies of the entire distribution, not only a package manager. Believe me, if you made one for Gentoo, it wouldn't look simple either.
Guix automatically builds and maintains dependencies.
Give me one package manager you can use without having packages defined first.
I though those are Gentoo users who like customizations and having control over the system. Of course you have to do customizations yourself, nobody is going to rice your desktop or use specific kernel settings for you. And it seems Gentoo is all about that, strange USE flags, all these instructions on the wiki, it doesn't even have an installer. Is there a fairy under the hood that makes everything work on Gentoo?
Actually Scheme is a multi paradigm programming language the code of the package manager is not functional, but the package manager is functional - it treats package definitions, dependencies and source code as input data, then the data is processed and you get a compiled program - output data. input -> function -> output
Scheme is great, because its syntax can be extended by for example macros, giving you a great flexibility - you can define your own domain specific language using Scheme.
They're actually handy and after a month coding Scheme you stop seeing them, also people thing you're a wizard.
Spank me daddy.

I was asking about you (though you are probably a different fag, but it matters not). And I am not interested in that shilling. Users may use their home directory for anything still.
The point was that you would complicate it even further by adding more versions of the shit. Gentoo has package slotting too, but I find it just better to overwrite the old package and be done. Less to think about that way. Having multiple versions of the same package is a rare necessity and more of a luxury. You still can chroot into some different system if you want though.
Like, all these arguments add up to how the Guix is generally unnecessary as fuck. That post above was correct in that it is a niche distro, like, even more so than Gentoo.
Binary packages will generally do that for you, like, you don't have a whole script for them, but that obviously wasn't the point. The point is you don't have to maintain your whole lot of immutable piece of shit package definitions. Like, writing EVERYTHING down is not a good idea, really, and you guix shills give it as a major selling point for some reason.
BTW I hate everyone who uses -O3 in /etc/portage/make.conf (globally) PERSONALLY. I swear to Christ, if you say shit like that to me IRL I will punch you in the face, and once you fall down, I will start kicking you into everything until you stop moving.
There actually isn't and the most annoying shit about the portage in general is that you have to record USE flags in some files just to install some package, like,
a) you ran emerge shit
b) package shit wants some USE flag enabled in some other package
c) PIECE OF SHIT PORTAGE WANTS ME TO MAINTAIN A FUCKING RECORD SOMEWHERE LIKE WHAT THE FUCK DUDE YOU MAINTAIN THE PACKAGE DATABASE WITH ALL THE USE FLAGS AND SHIT HOW HARD IS IT TO JUST ENABLE THEM AND ASK ME IF I WANNA REBUILD THE PACKAGES??????////
And before I forgot, Guix is even worse, like, I have read that to define a package you have to include WHOLE LIST OF DEPENDENCIES OR ELSE THEY WON'T GET INCLUDED INTO THE ENVIRONMENT AND YOUR BUILD JUST BREAKS. Tell me this is a good design and not some braindamage, and I will shit on you even harder.
Oh look, great, you have LISP braindamage.
If I was that autistic and good at writing lexers/parsers/compilers I would write my language using basically anything right fucking now, OK? I'm picking a language to write my OS BTW, and I'm thinking Ada. Tell me this is a good/bad idea.
I don't want to use anything LISP ever, OK? I want to allocate my limited brain resources to something better than validating paretheses sequences. Just add []{} to this shit at least, OK?

Chocolatey is overengineered garbage. Use scoop.sh/ instead.
(sage for offtopic)

Putting packages there would be unnecessarily redundant and a totally irreproducible mess.
Yes, I'm a different fag, you have to wait for the first one, because I'm only a minor Guix shill.
It would be complicated for any other package manager, but Guix (or Nix) makes it easy to use - it tracks and manages multiple versions of the same package - you don't have to have a different system to run software or uninstall incompatible packages anymore, because Guix solves this, by separating packages. People fear having different versions of the same software, because their package managers often shit everything into /usr/ or /usr/local or whatever different directory making a file spaghetti. Why should it be like this?
AFAIK, package definitions are mutable, the thing that is immutable is the store, where derivations (built packages) are kept.

-Os is actually often better, especially for slower/lower-end machines with smaller caches. Especially ARM in my experience profits from -Os.