The Linux & BSD Distro Tier List (20XX Edition)

Uses 'respect the operator' as a vague, subjective metric — Loaded Language (45/100)

At 0:00

Trying to turn 'vibes' into a formal metric. Using 'respect' is just emotional fluff 🎭

Why this score: He's using anthropomorphic language like 'respect' to define a technical ranking. It sounds profound, but it's actually just a subjective feeling masquerading as a rubric.

Original quote: “For the rubric of the tier list. It is simple. The question is, does this operating system respect the operator? If yes, it's going to go high on the list. If no, it's going to go low.”

Sets up 'operator friendliness' as the sole metric for ranking 🚩 — Missing Context (45/100)

At 0:40

He's making up a rule and calling it the law. Total moving target 🎯

Why this score: He claims 'operator friendliness' is the main factor but doesn't define it, leaving the entire ranking up to his personal vibe and 'daily driving' experience.

Original quote: “the main factor will be operator friendliness. If I didn't include a distro on this list, it's probably because I either haven't daily driven it long enough to give it a fair breakdown or I didn't want to include a fork of a fork”

Labels Fedora as 'peak' because it serves beginners and elitists 🎭 — Loaded Language (45/100)

At 1:00

Using 'peak' and 'excellent' to mask the fact that this is just his opinion 🙄

Why this score: He uses high-status labels like 'peak' and divides the community into 'beginners' and 'elitists' to justify a subjective ranking without technical proof.

Original quote: “Fedora Linux. This is going to be going into peak... Fedora is one of those distros that's an excellent choice for both groups.”

Claims DNF is 'bleeding edge' yet stable with a predictable cycle 🛡️ — No Frame (75/100)

At 2:00

Actually providing specific technical reasons for his stance. No games here 🤝

Why this score: He cites specific components like DNF and udev, along with a known 6-month release cycle, providing actual substance to his 'peak' rating.

Original quote: “Its package manager, DNF, is bleeding edge enough so that you're not running Debian tier software from 2015, but it's also stable enough so that udev doesn't randomly break every update. The release cycle is 6 months, predictable, well-communicated, and well-audited.”

labels Ubuntu 'slop' due to bloat and corporate-focused design — Loaded Language (45/100)

At 2:40

Using 'slop' and 'Debian for customers' to make a technical critique feel like a roast 💀

Why this score: He uses highly emotive, derogatory language ('slop', 'Debian for customers') to frame Ubuntu's evolution. While the sentiment is shared by many, it's a heavy-handed rhetorical attack.

Original quote: “Conversely here, I'm going to put Ubuntu in the slop tier. It's supposed to be beginner-friendly, but honestly, it's so bloated out of the box, and its package manager is decades behind what I consider to be usable. Ubuntu started off as Debian for humans and ended up as Debian for customers.”

recommends Fedora to everyone from newbies to pros — No Frame (75/100)

At 3:01

Broad recommendation but it's grounded in his previous points. Clean 💎

Why this score: He is making a subjective recommendation based on the technical stability he just established, which falls under 'no frame' for an opinion-based video.

Original quote: “So, all that being said, Fedora is peak and I recommend it to beginners who are just starting my Linux journey, as well as advanced users looking for something rock solid.”

Claims the primary benefit of Arch is social bragging rights 😈 — Loaded Language (45/100)

At 4:30

Selling a technical distro as a personality trait. Pure social clout bait 💀

Why this score: He's pivoting from technical control to the 'social flex' of using Arch, which is a classic emotional hook for enthusiast communities.

Original quote: “you can tell all your friends that you use Arch, by the way. And that is really the main reason to be using Arch.”

Promotes AUR as a convenience tool for non-official packages 🍒 — No Frame (75/100)

At 5:20

Just stating how the AUR works. No tricks here, just facts 🛠️

Why this score: This is a straightforward description of the AUR's function within the Arch ecosystem. No heavy-handed persuasion.

Original quote: “The AUR is great for convenience. You can grab stuff that is not in the official Pacman repositories.”

Admits his ranking is biased by his own content history 🚩 — Dubious (45/100)

At 6:20

Admits he's biased by his own niche expertise. Self-fulfilling hype 🤡

Why this score: He explicitly calls out his own bias, admitting that his preference for NixOS is tied to the fact that he's already an expert/advocate for it.

Original quote: “it's probably no surprise to you that I'm putting NixOS as goat here, seeing that I've made several videos specifically about NixOS”

labels NixOS as 'the goat' based on his own content history — Cherry-Picked (45/100)

At 6:30

He's making it the 'greatest of all time' just because he likes talking about it. Pure bias 🍒

Why this score: He's using his own niche expertise and video history as a proxy for universal superiority. It's not about the software; it's about his own obsession.

Original quote: “if you are a fan of the channel, it's probably no surprise to you that I'm putting NixOS as goat here, seeing that I've made several videos specifically about NixOS”

compares NixOS cleanliness to the 'messy' cleanup of Arch Linux — False Equivalence (45/100)

At 7:20

Comparing a specialized functional system to a standard rolling release is a massive reach 🚩

Why this score: He's framing standard package management as 'messy' and 'unclean' just to make his preferred method look like magic. It's a comparison of two different philosophies, not a failure of one.

Original quote: “On a legacy distro such as Arch, I would have to run something like sudo pacman -S CMatrix, and then I'd have to run CMatrix, and then in order to uninstall that, I'd have to run sudo pacman -Rns CMatrix, and then pray that pacman actually cleaned everything up.”

Nix dev shells work on any machine without setup — Dubious (45/100)

At 8:40

Claiming it works on 'any machine' is a massive stretch. 💀

Why this score: He's selling the convenience of Nix dev shells as a universal solution, but hardware architecture and existing environment conflicts still exist. It's high-confidence hyperbole.

Original quote: “I'm going to be entering the dev shell of oxwm, and this is on any machine. So, I immediately will have all the dependencies to build and test that project.”

Nix has a unique advantage over other package managers — No Frame (75/100)

At 9:10

Actually calling out the lack of a direct equivalent in other managers. No tricks here, just facts. 🟢

Why this score: He's pointing out a specific functional difference in how Nix handles transient execution compared to traditional package managers like apt or dnf. It's a legitimate technical observation.

Original quote: “run something like disk through Nix packages without installing it. Super quick way to check stats on my computer such as disk space or whatnot. And there's no real equivalent for DNF, Pac-Man, or apt.”

Nix allows for granular package pinning to prevent regressions — No Frame (75/100)

At 10:20

A very specific technical benefit that actually holds water. No fluff. 🟢

Why this score: This describes a core functional feature of Nix's dependency management. It is a verifiable technical capability rather than an emotional appeal.

Original quote: “If a single package regresses, I can pin that package to an older version and keep updating everything else normally.”

Claims NixOS solves the stability vs. updates debate by making it granular — False Equivalence (20/100)

At 10:40

He's treating a technical configuration choice like it's a philosophical revolution. 💀

Why this score: He equates the ability to pin specific packages with a total victory over the 'stability vs. bleeding edge' debate, ignoring that most users just want a system that works without constant manual intervention.

Original quote: “Every other distro forces you to pick globally. You're either on stable or everything is old, but on NixOS, you can just literally decide which package is going to be stable”

Sources: NixOS: A Paradigm Shift in System Stability and Reproducibility, NixOS Linux review, is it really the alternative to Debian and Archlinux ?, r/NixOS on Reddit: Is nixos really stable?

Describes the 'Gentoo paradox' of custom compilation vs. convenience — No Frame (75/100)

At 12:40

Just calling out the obvious trade-off of a niche distro. No tricks here, just reality 🛠️

Why this score: He's identifying a fundamental tension in the user experience of Gentoo—the time investment required for optimization. It's a logical observation rather than a manipulative frame.

Original quote: “So, yeah, compiling Firefox for a few hours can be annoying, but there are binary packages available as needed. Although, I would consider that going against the spirit of Gentoo and missing the point of it. Something I like to refer to as the Gentoo paradox.”

Uses personal experience to demote Gentoo below NixOS — Personal Story (60/100)

At 13:40

He's making a massive leap from his own setup to a universal ranking. That's one man's opinion 💀

Why this score: The speaker is using his personal transition from Gentoo to NixOS as the primary justification for why a major distribution isn' de 'GOAT' tier. While valid as an anecdote, it's a subjective pivot based on his specific workflow.

Original quote: “Why is Gentoo not in goat tier? Well, it was goat tier for me for a long time until I encountered NixOS. Being forced to be FHS compliant and not being able to systematically declare and reproduce my system without hacking together a bunch of POSIX sh scripts is why it's not goat.”

Claims Artix is just Arch with a different init system — False Equivalence (20/100)

At 14:30

Calling it 'just Arch' is a massive simplification to justify the mid-tier rank 💀

Why this score: He's stripping away all the nuance of why someone would actually use a different init system to make his dismissal feel more logical.

Original quote: “Artix is definitely daily drivable for me, but it's, as I said before, literally just Arch with a different init system.”

Sources: r/artixlinux on Reddit: To those of you who use Artix Linux, how has the experience been so far?, Artix Linux – Artix Linux is a fork of Archlinux to use different init systems, Artix Linux: Specs & Features | Linux Basecamp

Claims Artix repos lag behind Arch and break AUR compatibility — No Frame (75/100)

At 14:55

Actually citing specific technical friction points like AUR compatibility and repo lag 🛠️

Why this score: He's providing actual technical consequences of the architecture rather than just using vague adjectives.

Original quote: “Artix breaks a meaningful chunk of the AUR packages because they assume systemd, and their repos also lag behind Arch's, sometimes by hours, sometimes by days”

Labels Artix a 'protest distro' via external reference — Loaded Language (45/100)

At 15:40

Using 'protest distro' to wrap a technical opinion in emotional baggage 🚩

Why this score: He's using someone else's loaded label to avoid having to define the distro's value proposition himself.

Original quote: “I do like Artix. It's an incredible distro, but it's, as DT referred to it before, a protest distro, and I sort of agree with that.”

Claims Alpine is 'goat tier' if the rubric changes — False Dilemma (20/100)

At 16:20

Moving the goalposts just to make a 'mid-tier' choice look like a winner 🚩

Why this score: He's creating a hypothetical scenario where his current ranking doesn't apply just to satisfy the 'goat tier' hype.

Original quote: “If the rubric was changed to what is the best distro to run in a container, then yeah, Alpine would be goat tier.”

Sources: Goat Format Tier List 2026: Every Deck Ranked and Explained (August Update) | Goat World Blog | Goat World, Alpine Grade Systems - #grade #climbinggrades #climbing ..., Alpine (French Alpine) | Goat Breed Guide | WARN

Claims Alpine is 'goat tier' for containers via a hypothetical pivot — False Dilemma (45/100)

At 16:30

He's playing with the rules to make it sound like a winner. That's not a ranking, that's a pivot 🚩

Why this score: The speaker creates a hypothetical scenario where his current ranking is invalidated just to praise the distro's strengths. It's a way to avoid calling it 'mid-tier' by changing the goalposts.

Original quote: “If the rubric was changed to what is the best distro to run in a container, then yeah, Alpine would be goat tier.”

Claims near-impossible software compatibility issues via emotional framing — Loaded Language (45/100)

At 17:00

'Impossible' and 'madness' are doing heavy lifting here. It's a vibe, not a technical spec 💀

Why this score: Using high-intensity words like 'impossible' and 'madness' to describe package management struggles makes a technical hurdle sound like an existential crisis.

Original quote: “it's nearly impossible to get stuff like Kdenlive or OBS working correctly without some flatpak madness”

Claims a 'mid-tier' status is actually 'excellent' via contradictory framing — Volume Game (45/100)

At 18:20

He calls it 'mid-tier' then immediately pivots to 'excellent.' Pick a side, man 💀

Why this score: The speaker creates a contradiction by labeling the distro as 'mid-tier' but then uses high-praise language like 'excellent,' making the original ranking feel like a soft-pedal.

Original quote: “it's still young and the package coverage isn't quite there yet. Even though it's quote mid-tier for 20XX, I think it's still an excellent distro”

Ranking FreeBSD as 'peak' despite it not being Linux via a scope pivot — No Frame (75/100)

At 18:40

He's being honest about the category error before he makes it. Clean pivot. 🟢

Why this score: The speaker acknowledges the technicality that FreeBSD isn't Linux, which prevents him from being caught in a false equivalence trap.

Original quote: “let's move on to the BSDs here, and we'll start with FreeBSD. I'm going to be putting FreeBSD in peak tier. and yeah, I know it's not technically a Linux distro, but I'm doing a tier list on operator-friendly operating systems.”

Hyperbolic praise for documentation and naming conventions — Loaded Language (45/100)

At 20:00

Calling it 'the second best on the entire internet' is pure emotion, not data. 🎭

Why this score: He uses extreme superlatives ('best name in existence', 'second best on the internet') to build hype rather than providing objective metrics.

Original quote: “The handbook is the second best documentation on the entire internet after the Arch Wiki, of course. The pkg package manager has the best name of any package manager in existence.”

Dismissing Jails as 'not corporate slop' to justify its tier — Loaded Language (45/100)

At 20:20

Using 'corporate slop' to make a technical choice feel like a moral victory. 💀

Why this score: He uses loaded, emotional descriptors like 'corporate slop' and 'gimmick' to frame the technical utility of Jails as a way to avoid modern industry trends.

Original quote: “Jails are containers, but not corporate slop. So, overall, I mean, FreeBSD is an operating system that is not a gimmick, and it really is daily drivable.”

Predicts a corporate takeover of BSD via a 'thin wrapper' — speculative future-casting — Emotional Button (45/100)

At 20:40

Using a corporate boogeyman to justify a ranking choice. Purely emotional projection 💀

Why this score: He's using the fear of corporate 'slop' and a specific company (Palantir) to manufacture a reason why FreeBSD isn't in the top tier. It's not about the code; it's about the anxiety of ownership.

Original quote: “nothing in is stopping Palantir from taking the BSD kernel and putting a thin proprietary wrapper around it, calling it Palantir OS”

Lists technical advantages to claim FreeBSD is superior — cherry-picking features — Cherry-Picked (20/100)

At 21:20

Just a laundry list of features to win an argument. He's ignoring the trade-offs 🍒

Why this score: He is listing specific technical wins (ZFS, GPU support) to justify a ranking, but he's omitting the complexity or stability trade-offs that might make someone choose OpenBSD instead.

Original quote: “since FreeBSD is out there, you already get ZFS, faster GPU support, Linux binary escape hatches, and a fresher selection of ports”

FreeBSD is better than OpenBSD due to ZFS, GPU, and fresher ports — a subjective ranking presented as fact. 😈 — Just Vibes (50/100)

At 22:30

He's listing features and then declaring one 'better' than the other. That's not a metric, that's a preference. 💀

Why this score: The speaker presents a list of features (ZFS, GPU support, fresher ports) as objective reasons why FreeBSD is 'better' than OpenBSD. However, 'better' in this context is highly subjective and depends entirely on the user's priorities and use case. OpenBSD prioritizes security and code auditability, which might make it 'better' for some users despite lacking these specific features. It's a subjective opinion framed as a definitive ranking.

Original quote: “get ZFS, faster GPU support, Linux binary escape hatches, and a fresher selection of ports, which would make FreeBSD better than OpenBSD on the tier list here.”

Acknowledges security trade-offs but dismisses them as not 'moving the needle' for peak tier. 😈 — Volume Game (45/100)

At 22:40

He says security 'definitely matters' then immediately says it doesn't matter enough. That's a classic volume game. 🔥

Why this score: The speaker acknowledges a significant trade-off—less code auditability and weaker default security—and even states these 'definitely matter.' However, he immediately minimizes their impact by claiming they are 'not enough to move the needle' for OpenBSD's tier ranking. This is a volume game: a loud acknowledgment of a negative, followed by a quiet dismissal of its actual consequence, making it seem like he's considered all angles while still pushing his preferred narrative.

Original quote: “there is a trade-off to all these conveniences, and in this case it's going to be less code auditability and weaker default security ops, which definitely matter, of course, but are not enough to move the needle on pushing OpenBSD to the peak tier.”

Declares Void 'almost peak' but then places it in 'mid' tier for 'a couple reasons.' 😈 — Confidence Mismatch (45/100)

At 23:00

He says 'almost peak' then shoves it in 'mid' tier. That's not 'almost peak,' mortal, that's just 'mid.' 💀

Why this score: The speaker introduces Void Linux by stating it's 'almost peak' and lists positive attributes (minimal, runit, rolling release). However, he then immediately contradicts this by placing it in the 'mid' tier, citing 'a couple reasons' that he promises to explain. The initial 'almost peak' statement creates a confidence mismatch with the actual ranking, setting up a false expectation that the reasons for its lower placement must be minor, when in fact they are significant enough to drop it two full tiers in his system.

Original quote: “And for me, Void is almost peak. It's a super minimal system, it's got runit, and it's on a rolling release schedule, but it can't be peak for a couple reasons, and I'm going to explain why here, but I'm going to have to put Void in mid.”

Calls creating an alias a 'silly workaround' while criticizing the lack of parallel downloads. 😈 — Loaded Language (45/100)

At 23:40

Calling a common shell customization a 'silly workaround' is just loaded language to make his point. 🔥

Why this score: The speaker dismisses creating an alias—a standard and widely used practice in Linux to customize commands for convenience—as a 'silly workaround.' This loaded language is used to amplify his criticism of the package manager, framing a user-empowering solution as an undesirable hack, rather than acknowledging it as a flexible feature of the shell environment. It's designed to make the perceived flaw seem worse than it is.

Original quote: “And having to create an alias to fix this is a silly workaround. Also, xbps doesn't have parallel downloads.”

Claims lack of parallel downloads is 'noticeably slower' for fresh installs in 2028. 😈 — Confidence Mismatch (45/100)

At 24:00

He's talking about 2028 like he's already there. Bold prediction, mortal, but we're in 2026. 💀

Why this score: The speaker makes a definitive statement about performance in '2028,' claiming the lack of parallel downloads is 'noticeably slower' for fresh installs. While the general point about parallel downloads affecting speed is valid, making such a specific, confident claim about a future year (2028, when the current date is 2026) without any specific future-dated evidence or benchmarks is a confidence mismatch. He's projecting current observations into a future scenario with certainty he hasn't earned.

Original quote: “And to combat the Void shills, yes, it is incredibly fast anyway on a small update, but on a fresh install, not having parallel downloads in 2028 is noticeably slower for me.”

Missing parallel downloads is a sign of low priority via subtle signaling — Loaded Language (45/100)

At 24:40

Using one missing feature to indict an entire team's priorities. That's some heavy-handed signaling 🚩

Why this score: He's taking a single technical omission—parallel downloads—and turning it into a psychological 'signal' about the maintainers' intent. It's an emotional leap from a single data point.

Original quote: “Not having this feature in the package manager signals to me that it's not a priority for the maintainers. And yeah, they are working hard and for never, so I get that, but it is a minor minus one on the tier list rubric for me.”

Void is just Arch without systemd and less software — False Equivalence (20/100)

At 26:00

Calling it 'just Arch' is a massive simplification. That's not an analysis, that's a shortcut ❌

Why this score: He's stripping away the unique identity of a distribution by equating it to another through subtraction. It ignores the specific engineering nuances that define why someone would choose one over the other.

Original quote: “Void is kind of just Arch without systemd and with optional musl and less packages, so it belongs in mid-tier for me.”

Claims LFS is a 'rite of passage' via massive effort 💀 — Loaded Language (45/100)

At 26:40

Using his own 17-hour struggle to justify why it's a 'rite of passage' instead of just hard work 🎭

Why this score: He's using the sheer volume of his own labor as a proxy for the difficulty and 'importance' of the task. It's emotional weight applied to a technical project.

Original quote: “The LFS video took me 17 hours to record, so I had to condense 17 hours of footage into 3 and 1/2 hours for the tutorial video.”

Debian is only useful for old-school web servers due to 'boomer' documentation — Loaded Language (45/100)

At 28:30

Using 'boomer' and 'God's greatest gift' to turn stability into a generational insult 💀

Why this score: He's using loaded, emotional descriptors to frame Debian's massive documentation base as a relic of an old era rather than a functional asset.

Original quote: “The only reason this isn't going to go in slop tier is that I can in good faith recommend this to people who want to run some random Apache 2 PHP web server because there's so much documentation out there for boomers who think Debian is God's greatest gift to the Linux stability community.”

Debian's packages are outdated, citing specific version lags — Cherry-Picked (45/100)

At 28:49

Weaponizing specific version gaps to make a stable repo look ancient 🚩

Why this score: He's cherry-picking specific software (Zig, Go, Hugo) that requires bleeding-edge updates to make a case against a distribution built for stability.

Original quote: “Debian is the opposite of stable and the opposite of beginner friendly for me. Apt literally doesn't have Zig in the repos. It's 2028, and we don't have Zig? Not to mention Go is behind like six versions, and Hugo is like 40 versions behind. Rust is 10 versions behind.”

Slackware lacks dependency resolution, a technical fact used to justify its 'meh' status — No Frame (75/100)

At 30:40

Straight facts about package management. No tricks here, just the reality of manual library chasing 🛠️

Why this score: The speaker provides a specific technical reason for the ranking. It's an objective characteristic of the distribution's architecture.

Original quote: “Slackware's package tool doesn't have dependency resolution. So, you're going to have to chase libraries by hand.”

Dismissing Slackware as a daily driver based on personal usability standards — Personal Story (60/100)

At 31:20

He's making a usability judgment based on his own standards. Not science, just an opinion 🤷‍♂️

Why this score: He is pivoting from technical specs to a subjective 'feeling' of how it works for him. It's an assessment of experience, not a universal truth.

Original quote: “But, yeah, I really don't think it's that good for daily driving and I don't really think it's operator friendly.”

Red Hat is 'slop' because of subscription requirements, using loaded language — Loaded Language (45/100)

At 31:40

Calling a massive corporation 'slop' is pure attitude. He's weaponizing the friction of corporate bureaucracy 🤮

Why this score: The term 'slop' is highly emotive and subjective. While the requirement for subscriptions is a fact, the framing turns it into an emotional grievance against corporate structure.

Original quote: “The slop is everything else. You literally can't install RHEL without a subscription, an account, or agreeing to the corporate TOS”

Red Hat's shift to private source code is a betrayal of open source values — False Equivalence (45/100)

At 32:00

Equating 'private access' with a 'paywall.' It's a dramatic way to frame corporate access control 🚩

Why this score: He is making a moral argument by equating technical access models with the concept of a 'paywall.' It's an emotional interpretation of how Red Hat manages its intellectual property.

Original quote: “In 2023, Red Hat went further and shut down public access to the RHEL source code. So, the company that built its reputation on open source is now hiding its source behind a paywall”

Red pill on RHEL's source code secrecy via loaded language — Loaded Language (45/100)

At 32:30

Using 'hiding' and 'paywall' to turn corporate strategy into a heist movie 🕵️

Why this score: He's framing Red Hat's business model as a sleight of hand trick to make the user feel like they're being cheated out of open-source purity.

Original quote: “The company that built its reputation on open source is now hiding its source behind a paywall or a paying customer portal.”

Dismissing Ubuntu as 'slop' via aggressive loaded language — Loaded Language (45/100)

At 33:18

Calling Ubuntu 'slop' is a choice, not a technical metric 🤮

Why this score: He uses highly emotive, derogatory language to create an immediate emotional bias against a massive player in the space.

Original quote: “Why would you use Canonical slop when Debian exists if you're married to apt?”

Explains his personal choice to use Nix over Guix based on a single machine's setup — Personal Story (60/100)

At 35:00

Turns a single hardware limitation into a universal lifestyle choice. 💀

Why this score: He's using his own setup as the justification for a distribution choice, which is valid for him but turns an N=1 anecdote into his entire logic.

Original quote: “Why am I daily driving Nix instead of Guix on 90% of my machines? Well, because I only have one machine I can run the Libre kernel on and it's my favorite machine.”

Justifies missing entries as either lack of experience or avoiding 'forks of forks' — Missing Context (45/100)

At 35:40

Dismisses entire categories of software as 'forks of forks' to avoid the mess. 🚩

Why this score: He avoids the complexity of niche or derivative distributions by labeling them as 'forks of forks,' which simplifies his list but leaves out significant parts of the ecosystem.

Original quote: “If I didn't include a distro or BSD on this list, it's either because I haven't daily drove it long enough to talk about it or that I didn't feel the need to put a fork of a fork of a fork on here.”

Requests feedback to validate his opinions and drive future content — No Frame (75/100)

At 36:00

Just a standard wrap-up. No tricks here, just asking for the engagement he needs. 🤝

Why this score: This is a clean, standard outro used to build community and signal that his opinions are open to debate.

Original quote: “If you disagree with any of these placements, just let me know in the comments. And if you'd like to see any Linux, BSD, or free and open source software related content in the future, drop a comment and I will put it in the pipeline.”