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

Setting the stage for a definitive tier list — a bold claim for something so subjective. 😈 — Confidence Mismatch (45/100)

At 0:00

An 'official' tier list? That's not a thing, mortal. It's an opinion, dressed up in a badge. 💀

Why this score: Calling a personal opinion an 'official' tier list gives it an unearned authority. It's a subjective ranking presented as an objective truth, which is a classic move to make your take sound more important than it is.

Original quote: “What's up, guys? My name is Tony, and today we're going to do a quick and painless official Linux/BSD tier list.”

Labeling Fedora as 'peak' based on a subjective rubric 🚩 — Confidence Mismatch (45/100)

At 0:53

Declaring a winner before even explaining why. Pure unearned confidence 💀

Why this score: He's jumping straight to a high-tier verdict without providing the technical justification first. It's an emotional conclusion masquerading as a finding.

Original quote: “So, we're going to start this off with Fedora Linux. This is going to be going into peak”

Claiming Fedora serves two extremes without nuance 🎭 — Loaded Language (45/100)

At 1:40

Using 'beginners' and 'elitists' to justify a broad appeal. It's too clean 🚩

Why this score: He uses polarizing labels to make a generic claim about usability. It ignores the massive middle ground of intermediate users to create a false sense of universal appeal.

Original quote: “one of the things about the Linux community is that it has a lot of beginners and a lot of elitists. Fedora is one of those distros that's an excellent choice for both groups.”

Using 'bleeding edge' and 'stable enough' as vague metrics ⚖️ — Missing Context (45/100)

At 2:20

Vague comparisons to '2015 software' and 'random breaks'. No actual data 💀

Why this score: He uses relative terms like 'enough' to avoid having to cite actual version numbers or stability statistics. It sounds authoritative but lacks the hard metrics of a real audit.

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.”

claims Fedora's security response is 'peak tier' without data — Confidence Mismatch (45/100)

At 2:40

Calling security responses 'peak' based on vibes and history alone 💀

Why this score: He uses high-authority labels like 'peak tier' for security pipelines without citing actual response time metrics or recent audit data.

Original quote: “The Fedora devs have really fast CVE responses historically. So, all that being said, Fedora is peak”

uses a sharp analogy to claim Ubuntu prioritizes profit over users — Loaded Language (45/100)

At 3:20

That 'human vs customer' line is a killer bit of rhetoric 💀

Why this score: He uses a highly effective rhetorical pivot—contrasting 'humans' with 'customers'—to make a subjective critique feel like an undeniable truth.

Original quote: “Ubuntu started off as Debian for humans and ended up as Debian for customers. The technical decisions all point in one direction, away from respecting the operator”

labels Ubuntu as 'slop' due to bloat and old tech — Loaded Language (45/100)

At 3:40

Using 'slop' and 'decades behind' to trigger an emotional reaction 🤮

Why this score: He uses aggressive, derogatory descriptors like 'slop' and 'decades behind' to frame a massive corporation's software as outdated.

Original quote: “it's so bloated out of the box, and its package manager is decades behind what I consider to be usable.”

tells users to ditch Ubuntu for Fedora if they want non-APT — No Frame (75/100)

At 4:00

Just a straight-up recommendation based on his personal preference. Clean 🧼

Why this score: He's not playing tricks here; he's just stating his preference for a different ecosystem based on the user's tolerance for APT.

Original quote: “And if you're okay with a non-APT Debian is so easy to install these days. And if you're okay with a non-APT system, just use Fedora.”

Claims Arch is peak tier for being 'operator-friendly' without proof — Confidence Mismatch (45/100)

At 4:40

Calling it 'without a doubt' is heavy lifting for a subjective preference 💀

Why this score: He uses absolute certainty to describe user-friendliness, which is the most subjective metric in computing. No data provided on why it's 'friendly' yet.

Original quote: “Arch is without a doubt one of the most operator-friendly Linux distributions out there.”

Calls Arch Wiki the 'best ever' without comparison — Anonymous Authority (45/100)

At 6:00

The 'best ever' superlative is a classic trap. No metrics, just vibes 🚩

Why this score: He's making a superlative claim about quality without citing any comparative studies or user-satisfaction metrics from other wikis.

Original quote: “I think the Arch Wiki might be the best piece of Linux documentation that has ever been written.”

Calls NixOS 'the goat' and S tier for 'boomers' — pure opinionated hype 😈 — Confidence Mismatch (45/100)

At 7:00

Labeling a niche, complex distro as 'for boomers' is pure bravado without actual demographic data 💀

Why this score: He's assigning a massive, sweeping label ('the goat') to a highly technical distro and making a wild assumption about its user base being 'boomers' just to make a point.

Original quote: “NixOS is the goat distro in my opinion. That's going to be S tier for the boomers.”

Claims Nix shells make it 'OP' — using gamer slang to sell a feature 🎮 — Dubious (45/100)

At 8:00

Using 'OP' to describe a technical feature is just flavor text used to manufacture hype 🚩

Why this score: He's using high-energy, non-technical slang like 'OP' to describe the utility of Nix shells. It sounds more impressive than it actually is for a standard user.

Original quote: “So, first of all, the nix shells are one of the reasons why nix is so OP.”

Calling Arch a 'legacy distro' and implying its package management is inferior. 💀 — Loaded Language (45/100)

At 9:00

He calls Arch 'legacy' and then describes a standard package manager workflow as if it's some ancient ritual. That's not a critique, that's just being dramatic. 🔥

Why this score: The term 'legacy distro' is loaded language, implying Arch is outdated or inferior, when it's a rolling release known for being current. The description of pacman -Rns as 'praying' for cleanup is an exaggeration to make NixOS seem superior, ignoring that pacman is generally effective at dependency management.

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.”

Claiming Nix dev shells provide 'all dependencies' for projects 'on any machine.' 🚩 — Confidence Mismatch (45/100)

At 9:20

He says 'all dependencies' and 'on any machine' like it's magic. It's a powerful tool, sure, but 'all' and 'any' are doing a lot of heavy lifting there. 💀

Why this score: While Nix dev shells are excellent for reproducible development environments, stating 'all dependencies' and 'on any machine' without caveats is an oversimplification. It assumes the project's flake.nix is perfectly configured to capture every single dependency and that the Nix environment itself is set up correctly on 'any machine.' This is a confidence mismatch, presenting a powerful feature as universally flawless.

Original quote: “Another thing I love about nix is the dev shells. So, if we actually clone something like oxwm here, and then we cd into it, we see there's a flake.nix right there. And if I run nix develop . here, I'm going to be entering the dev shell of oxwm, and this is on any machine. So, I immediately will…”

Nix dev shells are the '20xx version of Docker containers' — a bold, unproven comparison. — Confidence Mismatch (45/100)

At 10:39

Calling Nix dev shells the '20xx version of Docker' is a huge leap. That's not a comparison, that's a prophecy. 🔮

Why this score: The speaker presents a strong, future-oriented claim comparing Nix dev shells to Docker containers, implying a significant evolution or replacement. This is a highly speculative statement, not a verifiable fact, and is delivered with unearned confidence. It's a 'just trust me, bro' for the future of tech. I've seen this trick since before your grandfather tried it.

Original quote: “nix dev shells are the [5:41] 20xx version of docker containers, and [5:44] it's probably the best thing about nix.”

Claims no 'real equivalent' to Nix run for other package managers — a sweeping dismissal. — Confidence Mismatch (45/100)

At 11:00

Declaring 'no real equivalent' for DNF, Pac-Man, or apt is a bold claim. It's a dismissal, not a comparison. 💀

Why this score: The speaker confidently states that there's 'no real equivalent' to Nix run's functionality in other major package managers. This is a strong, definitive statement that would require extensive knowledge of all package managers and their various tools and features to back up. It's presented as an absolute truth without any supporting evidence or nuance, which is classic confidence mismatch. I've seen mortals make this exact move a million times.

Original quote: “And there's no [5:57] real equivalent for DNF, Pac-Man, or [6:00] apt. This is something that is a nicety [6:02] [9:20] exclusive to the Nix package manager.”

Highlights NixOS's reproducibility and rollbacks as 'really good' features — a subjective assessment. — No Frame (75/100)

At 11:20

He's just stating common, well-known benefits of NixOS. No tricks here, just facts. ✅

Why this score: The speaker is describing core, widely recognized features of NixOS. Reproducibility and atomic rollbacks are indeed fundamental design principles and selling points of NixOS, and this statement aligns with common understanding of the system. It's a straightforward description, not a manipulative claim.

Original quote: “NixOS is really good because [6:08] of the reproducibility and the [6:10] rollbacks.”

Highlights per-package pinning as a 'big feature' nobody talks about — a subjective observation. — No Frame (75/100)

At 12:00

He's just sharing a feature he appreciates. It's a personal observation, not a claim. 👍

Why this score: The speaker is expressing a personal preference for a specific feature (per-package pinning) and noting that he feels it's under-discussed. This is a subjective opinion and a valid observation about community discourse, not a factual claim that requires external verification. It's a straightforward statement of personal experience and preference.

Original quote: “And one big feature that I like [6:34] that nobody really talks about is per [6:36] package pinning.”

Recounts a personal experience with Kdenlive update breaking workflow — an anecdote. — Personal Story (60/100)

At 12:20

He's just telling a story about his own experience. That's not a claim, it's a diary entry. 😈

Why this score: The speaker is sharing a specific, personal anecdote about a Kdenlive update breaking his workflow and how he used package pinning to resolve it. This is a personal experience, not a universal claim, and is presented as such. It serves to illustrate the utility of the feature he just described. I'm not here to fact-check someone's bad day.

Original quote: “This actually [6:44] happened to me recently with a Kdenlive [6:46] update. They pushed a release that broke [6:48] my workflow, so I had to pin Kdenlive to”

Every other distro forces a global choice: stable or old — a false dilemma. 🚩 — False Dilemma (20/100)

At 13:00

He's setting up a false choice: 'stable or everything is old.' That's not how most distros work. 😈

Why this score: This presents a false dilemma. Many distributions offer various repositories (e.g., testing, unstable, backports) or allow selective package updates, providing more nuanced control than a simple 'stable or old' global choice. It simplifies the landscape to make NixOS look uniquely superior.

Original quote: “Every other distro forces you to pick globally. You're either on stable or everything is old”

Sources: All Linux Distro Are Not the Same. Here's Why and How They Differ, r/linuxquestions on Reddit: If you had to pick ONE Linux distro for the next 5 years, what would you choose?, r/linux4noobs on Reddit: Help choosing distro needed: Arch mindset but no rolling updates?

NixOS throws Debian's stability and Arch's bleeding edge 'in the trash can' — a dramatic overstatement. 🔥 — Loaded Language (45/100)

At 13:20

To say it puts their arguments 'in the trash can' is pure hyperbole. It's a different approach, not a total invalidation. 💀

Why this score: This is loaded language designed to dismiss established, respected distributions. While NixOS offers a unique model, it doesn't magically invalidate the design philosophies or user bases of Debian (known for stability) or Arch (known for bleeding-edge). It's a strong claim without the evidence to back up such a definitive dismissal.

Original quote: “And that puts Debian's stability argument and Arch's bleeding edge argument both in the trash can.”

Comparing not trying NixOS to not seeing 'Breaking Bad' — a dramatic, self-serving analogy. 🎭 — False Equivalence (20/100)

At 13:40

Comparing a Linux distro to 'Breaking Bad' as 'the gold standard' is a ridiculous overreach to hype his preference. 🚩

Why this score: This is a false equivalence. Comparing a technical operating system to a critically acclaimed TV show as 'the gold standard' is a dramatic, emotional appeal. It attempts to elevate NixOS to an unparalleled status by implying that all other options are inherently inferior, which is a subjective and unprovable claim in the context of diverse user needs and preferences for operating systems.

Original quote: “If you've never tried NixOS, you're kind of in a unique position similar to somebody who's never seen Breaking Bad in that every other show seems fine to you because you've never seen the gold standard.”

Sources: Breaking Bad Explained By Analogy Metaphor Examples, Breaking Bad: Walter White as Nietzschean Hero - American Affairs Journal, Badly Broken: A Spoiler-Free Analysis of Breaking Bad as a Deeply Human Drama | Church Life Journal | University of Notre Dame

Gentoo is 'probably the most operator friendly' of 'legacy distros' — a subjective, vague claim. 🧐 — Loaded Language (45/100)

At 14:00

Calling Gentoo 'operator friendly' is subjective, and 'legacy distros' is a vague, loaded term. 💀

Why this score: The term 'operator friendly' is highly subjective, especially for a distribution like Gentoo, which is known for its steep learning curve and manual configuration. What one person considers 'friendly' (e.g., control) another might find 'difficult.' The phrase 'legacy distros' is also vague and potentially dismissive, used to frame Gentoo in a specific, perhaps outdated, light while still praising it in a niche way.

Original quote: “Gentoo is probably the most operator friendly Linux distribution of all legacy distros”

Gentoo offers 'almost full control' with specific component choices. No trick here. — No Frame (75/100)

At 14:30

He's just laying out the core appeal of Gentoo: granular control over system components. Straightforward.

Why this score: The speaker is describing the fundamental design philosophy of Gentoo, which is known for its high degree of user control over system libraries and init systems. This is a widely accepted characteristic of the distribution.

Original quote: “Well, the [7:48] answer is control. Gentoo gives you [7:50] almost full control of your system. You [7:51] can use musl libc or glibc, and use [7:55] OpenRC or systemd.”

Gentoo allows custom kernel compilation and specific CPU flag tweaks. Still just describing features. — No Frame (75/100)

At 14:39

Another feature description for Gentoo users. It's what the distro is known for, no spin here.

Why this score: The ability to compile a custom kernel and optimize with specific CPU flags is a well-documented and central feature of Gentoo, allowing for highly tailored and minimal system builds. This is an accurate description of its capabilities.

Original quote: “You can tweak your [7:57] compile [12:20] flags for your specific CPU. You [8:00] can [music] compile a custom kernel that [8:02] strips out every driver and feature you [8:03] don't actually use.”

Acknowledges long compile times but dismisses binary packages as 'missing the point'. — Volume Game (45/100)

At 15:00

He admits the pain point, then immediately dismisses the solution as 'missing the point.' That's how you give with one hand and take with the other. 😈

Why this score: The speaker presents a common criticism of Gentoo (long compile times) and then immediately offers a counterpoint (binary packages). However, he then undermines that counterpoint by stating it goes 'against the spirit of Gentoo,' effectively negating the practical solution for many users. It's a classic volume game: acknowledge a flaw, then quietly retract the practical fix.

Original quote: “So, yeah, compiling Firefox for a few [8:13] hours can be annoying, but there are [8:14] binary packages available as needed. [8:17] Although, I would consider that going [8:19] against the spirit of Gentoo and missing [8:21] the point of it.”

Claims fast systems don't benefit from Gentoo optimizations, and the paradox was 'less wide' in 2010. — Confidence Mismatch (45/100)

At 15:40

He's making a broad claim about 'any speed benefits' and a historical shift in 'paradox width' without a shred of data. Just his vibe. 💀

Why this score: The speaker confidently asserts that fast systems 'won't really notice any speed benefits' from Gentoo's optimizations, and that the 'paradox was a lot less wide back in 2010.' These are subjective claims about performance and historical applicability, presented as fact without any benchmarks, studies, or specific examples to back them up. It's personal experience dressed up as universal truth.

Original quote: “And then, for the systems [13:20] that [8:35] compile incredibly fast, you won't [8:37] really notice any speed benefits from [8:39] those optimizations anyway. So, this [8:41] paradox was a lot less wide back in 2010 [8:44] when I started using Gentoo, and it was [8:46] much more applicable to get…”

Gentoo was 'goat tier' for him until NixOS. Purely personal experience. — Personal Story (60/100)

At 16:20

He's just sharing his personal journey with distros. It's his opinion, not a claim about Gentoo's objective quality. 😈

Why this score: The speaker is explicitly stating his personal preference and experience ('it was goat tier for me'). This is a subjective opinion based on his individual use and discovery of NixOS, not a factual claim about Gentoo's universal standing. It's his story, not data.

Original quote: “and at [13:40] the time it was [8:49] required for certain things on the [8:51] hardware that I had available to me at [8:52] the time. So, why is Gentoo not in goat [8:55] tier? Well, it was goat tier for me for [8:57] a long time until I encountered NixOS.”

Gentoo was 'goat tier' until NixOS appeared — personal experience as a ranking factor. — Personal Story (60/100)

At 16:30

He's ranking based on his own journey. One man's 'goat tier' is another's 'never again.' 😈

Why this score: The speaker is explicitly stating his personal experience with Gentoo and NixOS as the reason for its tier placement. This is a subjective opinion based on his individual usage, not a universal technical assessment.

Original quote: “So, why is Gentoo not in goat [8:55] tier? Well, it was goat tier for me for [8:57] a long time until I encountered NixOS.”

Recommends Gentoo for full control without 'going insane' on Crux Linux — a subjective comparison. — Loaded Language (45/100)

At 16:40

He's recommending it, but 'going insane' is doing all the heavy lifting for why Crux is worse. 💀

Why this score: The phrase 'without going insane on Crux Linux' uses emotionally charged language to implicitly criticize Crux Linux without providing specific technical reasons. It's a subjective jab rather than a factual comparison.

Original quote: “It's really close, [9:11] though, and I recommend Gentoo to anyone [9:13] who wants to be [17:00] [14:20] in full control over [9:14] their system without going insane on [9:17] Crux Linux.”

Artix is 'daily drivable' but 'literally just Arch with a different init system' — a dismissive comparison. — Loaded Language (45/100)

At 17:00

He calls it 'daily drivable' then immediately dismisses it as 'literally just Arch.' That's a backhanded compliment, if I've ever heard one. 😈

Why this score: The speaker uses 'literally just Arch' to diminish Artix Linux, implying it lacks significant unique value beyond its init system. While technically true that it's an Arch fork, the phrasing is dismissive and loaded, downplaying its distinct features.

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

Artix breaks AUR packages due to systemd assumption and its repos lag behind Arch's — a specific technical critique. — No Frame (75/100)

At 17:20

A direct, specific technical critique of Artix's compatibility and repo update speed. No tricks here. 🔥

Why this score: The speaker provides concrete technical reasons for Artix's lower tier placement: incompatibility with AUR packages due to systemd assumptions and repository lag compared to Arch. These are specific, verifiable claims about the distribution's functionality and maintenance.

Original quote: “Artix breaks a meaningful chunk of the [9:57] AUR packages because they assume [9:59] systemd, and their repos also lag behind [10:02] Arch's, sometimes by hours, sometimes by”

Artix repos lag behind Arch, impacting security updates — a specific technical critique. — No Frame (75/100)

At 18:30

He's laying out a specific technical issue with Artix and its package management. No tricks here, just a direct observation.

Why this score: The speaker is detailing a technical problem with Artix's package management and its impact on security. This is a direct, verifiable claim about software behavior, not a rhetorical flourish.

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”

Calling Artix a 'protest distro' — using someone else's label to dismiss it. — Anonymous Authority (45/100)

At 18:40

He's using 'DT referred to it' to lend weight to his 'protest distro' label. Classic move to outsource the critique. 💀

Why this score: The speaker is attributing the 'protest distro' label to 'DT' (presumably another tech personality) rather than owning the characterization himself. This uses an unnamed or vaguely referenced authority to bolster his opinion, rather than providing direct evidence or a personal argument.

Original quote: “days, which really matters for security updates. I do like Artix. It's an incredible distro, but it's, as DT referred to it before, a protest distro,”

Despite 'operator respecting' features, Artix is 'mid-tier' — a subjective ranking. — Just Vibes (50/100)

At 19:00

He admits it's 'operator respecting' but still shoves it into 'mid-tier' based on 'everything I've said.' That's not a metric, that's a feeling. 😈

Why this score: The speaker acknowledges a positive attribute ('operator respecting') but then places Artix in 'mid-tier' based on a subjective synthesis of his previous points. This is a personal ranking based on his 'rubric,' not an objective, verifiable claim. It's his opinion, pure and simple.

Original quote: “operator respecting, but combining with everything I've said, I'm going to have to throw Artix in mid-tier.”

Alpine 'falls short' for desktop 'operator friendliness' — a subjective judgment. — Just Vibes (50/100)

At 19:20

He's judging Alpine by his 'operator friendly' rubric, which is just his personal preference. It's not a flaw, it's a mismatch to his taste. 😈

Why this score: The speaker is applying his subjective 'operator friendly' rubric to Alpine and concluding it 'falls short.' This is a personal assessment based on his defined criteria, not a universally verifiable fact about the distro's capabilities.

Original quote: “yeah, Alpine would be goat tier. But, since our rubric is more about what is friendly to the operator, Alpine falls short.”

Alpine is 'daily drivable for desktop Linux' for his workflow — a personal experience. — Personal Story (60/100)

At 20:00

He's sharing his own experience, saying it works for 'my workflow.' That's not a universal truth, just his personal anecdote. 😈

Why this score: The speaker is describing his personal experience with Alpine Linux, stating it's 'daily drivable for desktop Linux' specifically 'for my workflow.' This is a subjective account of his own use, not a claim about its universal suitability or a verifiable fact.

Original quote: “It is an incredibly lightweight distro based on musl instead of glibc with OpenRC instead of systemd, and honestly, for my workflow, it is daily drivable for desktop Linux.”

Alpine idles under 200MB RAM with X11 — a specific performance claim. — No Frame (75/100)

At 20:20

He's giving a specific, verifiable performance metric for Alpine. No spin, just a number. 😈

Why this score: The speaker is providing a specific, measurable performance claim about Alpine Linux's RAM usage at idle, even with X11. This is a direct statement of fact that could be empirically tested.

Original quote: “I do like that you can get a solid system idling under 200 megs [music] of RAM with ease, even with the bloat that comes with X11.”

Claims Alpine Linux is impossible for Kdenlive/OBS without Flatpak madness — a personal hurdle presented as a universal truth. 💀 — Confidence Mismatch (45/100)

At 20:30

He says 'nearly impossible' for Kdenlive/OBS. That's not a fact, that's his personal frustration wearing a cape. 😈

Why this score: The speaker presents his personal difficulty with specific software on Alpine Linux as a general impossibility. While it might be challenging for his workflow, 'nearly impossible' is a strong, definitive statement that lacks universal evidence and is likely an overstatement of his individual experience.

Original quote: “idling under 200 megs of RAM with ease, even with the bloat that comes with X11. But, besides that, it's nearly impossible to get stuff like Kdenlive or OBS working correctly without”

Paints Chimera's design choices as 'on purpose' and 'coherent' while implying Alpine's were accidental. 🚩 — False Equivalence (20/100)

At 20:40

He's elevating Chimera's design as 'on purpose' and 'coherent' against Alpine's 'because it was built for containers.' As if Alpine's design wasn't also deliberate for its intended use. 💀

Why this score: The speaker creates a false equivalence by contrasting Alpine's design (built for containers) with Chimera's (made 'on purpose' as a 'coherent project'). This implies Alpine's design choices were less intentional or thought-out, when in reality, Alpine's stripped-down nature is a deliberate and coherent design choice for its specific use case (containers and embedded systems).

Original quote: “Alpine ended up with musl and stripped out a userland because it was built for containers, but Chimera made the same choices on purpose as a coherent project that questions whether the GNU userland belongs in modern Linux distributions at all.”

Sources: Chimera Linux enters beta – OSnews, Chimera Linux - Wikipedia, Why Chimera Linux - Wesley Moore

Declares Chimera 'daily drivable for me' then immediately contradicts it for 'most people.' 🍒 — Volume Game (45/100)

At 21:20

He says it's 'totally daily drivable for me' then immediately adds 'it won't be daily drivable for most people.' That's a classic volume game: make a bold claim, then quietly retract it. 😈

Why this score: The speaker uses a 'volume game' by making a strong personal claim ('totally daily drivable for me') only to immediately qualify and effectively retract it for the majority ('won't be daily drivable for most people'). This allows him to sound confident while simultaneously covering his bases, making the initial claim less impactful than it first appears.

Original quote: “and it's totally daily drivable for me, especially because my workflow is simply a terminal and web browser. But, similar to Alpine, it won't be daily drivable for most people,”

FreeBSD's integrated kernel, userland, and ports as a key differentiator — a straightforward description. — No Frame (75/100)

At 22:40

He's just laying out the architectural difference. No tricks here, just a technical explanation. 😈

Why this score: The speaker is describing a well-known architectural distinction between FreeBSD (a complete operating system) and Linux distributions (which combine a kernel with various userland components). This is a factual statement about their design philosophies, not a manipulative frame.

Original quote: “The big [12:20] difference between FreeBSD and every [12:23] Linux distro on this list is that the [12:24] kernel, the userland, and the ports are [12:27] all in one project.”

Contrasting Linux's modularity with FreeBSD's integrated development — a clear comparison. — No Frame (75/100)

At 23:00

Again, just explaining the fundamental difference in how these systems are built. It's a basic technical fact. 😈

Why this score: This is a direct continuation of the previous point, detailing the modular nature of Linux distributions versus the integrated development of FreeBSD. It's a standard technical comparison, not an attempt to mislead or frame unfairly.

Original quote: “It's all developed [12:30] together. Whereas on Linux, you have the [12:32] Linux kernel, you've got whatever [12:34] userland the distro chose to put on top [12:36] of it, and then you've got the [music] [12:37] package manager.”

Claiming a 'feelable difference' in daily use due to FreeBSD's integration, tying it to user-friendliness. — Confidence Mismatch (45/100)

At 23:20

He says you can 'feel the difference' like it's a universal truth. That's not a fact, that's a subjective experience presented as objective. 💀

Why this score: While the architectural differences are real, claiming one can 'actually feel the difference' in day-to-day use and that this inherently makes it 'operator-friendly' is a subjective assertion presented with objective certainty. User experience is highly personal, and what one person finds 'friendly' another might find cumbersome. It's a leap from technical design to universal user perception without evidence.

Original quote: “And since FreeBSD is [12:39] [19:40] really just one conglomeration of [12:41] everything, it is one operating system, [12:43] and you can actually feel the difference [12:45] when you use it day-to-day, which makes [12:46] it operator-friendly”

Ranking the FreeBSD handbook as the 'second best documentation' after the Arch Wiki. — Confidence Mismatch (45/100)

At 23:40

Second best on the 'entire internet'? That's not a metric, mortal. That's just an opinion wearing a crown. 💀

Why this score: While both the FreeBSD Handbook and the Arch Wiki are highly regarded for their quality, declaring one 'second best' on the 'entire internet' is a subjective opinion presented as an objective ranking. There's no universal metric or authority to make such a definitive claim about all documentation across the internet.

Original quote: “The handbook is [12:58] the second best documentation on the [13:00] entire internet after the Arch Wiki, of [13:02] course.”

Describing FreeBSD Jails as 'containers, but not corporate slop' and FreeBSD itself as 'not a gimmick' and 'daily drivable'. — Loaded Language (45/100)

At 24:00

Calling other containers 'corporate slop' is just emotional button-pushing. And 'not a gimmick' is just begging the question. 🚩

Why this score: The phrase 'not corporate slop' is loaded language designed to evoke a negative emotional response towards other container technologies (like Docker) without providing specific, objective criticisms. Similarly, stating FreeBSD is 'not a gimmick' is a defensive assertion that implies others might think it is, rather than a neutral description. While 'daily drivable' is a common term, the preceding loaded language frames the entire statement with a bias.

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

BSD's license is an "empty text file" allowing Palantir to make a proprietary OS — a hypothetical scenario presented as a certainty. 💀 — Emotional Button (45/100)

At 24:40

He's painting a doomsday scenario with Palantir, using a hypothetical future to justify his dislike of the license. That's not analysis, that's a horror story. 😈

Why this score: The speaker uses Palantir, a company often associated with surveillance and government contracts, to evoke fear and distrust. He then presents a speculative future where Palantir creates a proprietary OS from BSD as if it's an inevitable outcome, rather than a possibility. This taps into user anxieties about corporate control and open-source principles to make his point about the license, rather than focusing on the technical merits or actual current uses.

Original quote: “The license [13:22] is literally an empty text file. [music] [13:23] Nothing in is stopping Palantir from [13:26] taking the BSD kernel and putting a thin [13:28] proprietary wrapper around it, calling [13:30] it Palantir OS”

Predicts a "government-mandated" Palantir OS by 2035, unreadable and unmodifiable — a specific, unevidenced future. 🔮 — Confidence Mismatch (45/100)

At 25:00

He's predicting a specific, dystopian future for 2035 with absolute certainty. That's not a prediction, it's a fan-fiction with a deadline. 💀

Why this score: The speaker presents a highly specific and alarming future scenario (government-mandated Palantir OS by 2035, unmodifiable) as if it's a foregone conclusion. There's no evidence provided to support such a precise and dramatic prediction, especially one so far in the future. This is a classic confidence mismatch, where the certainty of the claim far outstrips any available evidence, used to amplify the emotional impact of his argument against the BSD license.

Original quote: “installing it on [13:33] every government-mandated laptop that [13:35] you [21:00] will be required to use [music] in [13:36] 2035, which you won't be able to read, [13:39] modify, or redistribute the source code”

Dismisses counter-arguments about the license not mattering, stating "for me it does" — personal preference overriding broader discussion. 🤷 — Personal Story (60/100)

At 25:20

He acknowledges a counter-argument, then just says 'for me it does.' That's not a rebuttal, it's just shutting down the conversation with personal feelings. 😈

Why this score: The speaker briefly acknowledges that 'you can make an argument that the license doesn't matter,' but immediately dismisses it by stating 'but for me it does.' This shifts the discussion from a potentially objective analysis of license implications to a subjective personal preference, effectively sidestepping a deeper engagement with opposing viewpoints. While personal opinion is valid, presenting it as the final word after acknowledging other arguments is a rhetorical shortcut.

Original quote: “essentially it'll be unfree BSD. [13:43] [music] So, in terms of operator [13:45] friendliness, yeah, you can make an [13:46] argument that the license doesn't [21:20] [13:47] matter, but for me it does”

Claims OpenBSD has the "best security model in the industry" but is a "pain for desktop use" — a trade-off presented as fact. ⚖️ — No Frame (75/100)

At 25:40

He's making a direct claim about security and a practical observation about usability. It's a common trade-off, stated plainly. 😈

Why this score: The speaker asserts that OpenBSD has the 'best security model in the industry' and is based on 'excellent first principles' like least privileges. He then immediately contrasts this with the practical reality that 'daily driving it is going to be a pain for desktop use.' This presents a straightforward trade-off between security and user-friendliness, which is a common and generally accepted characteristic of OpenBSD, without any apparent rhetorical manipulation.

Original quote: “OpenBSD has the best security model in [14:09] the industry, and it's based on [14:10] excellent first principles such as the [14:12] principle of [22:00] least privileges, but daily [14:14] driving it is going to be a pain for [14:16] desktop use.”

FreeBSD is better than OpenBSD due to ZFS, GPU, Linux binary escape hatches, and fresher ports. 😈 — No Frame (75/100)

At 26:40

He's laying out the technical reasons he prefers FreeBSD. It's a clear comparison of features. 🔥

Why this score: He's directly comparing technical features like ZFS support, GPU performance, and port freshness between FreeBSD and OpenBSD. This is a straightforward technical assessment, not a rhetorical trick. It's a preference based on stated criteria.

Original quote: “you already 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 trade-offs for FreeBSD (less auditability, weaker security) but dismisses them as not enough to change the tier. 💀 — Volume Game (45/100)

At 27:00

He mentions 'weaker default security' and then immediately waves it off. That's not a trade-off, that's a quiet dismissal. 🚩

Why this score: He brings up significant downsides—less code auditability and weaker default security—but then quickly minimizes their impact on his tier list. It's a classic volume game: state a major flaw, then immediately lower its perceived importance so it doesn't actually affect the conclusion. He's acknowledging it, but not really weighing it.

Original quote: “And of course, 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.”

Void Linux is 'almost peak' but gets relegated to 'mid' for 'a couple reasons' he'll explain. 😈 — No Frame (75/100)

At 27:40

He's setting up his argument for why Void isn't top tier. It's a clear premise for his upcoming points. 🔥

Why this score: He's stating his initial assessment of Void Linux and setting the stage for his detailed reasoning. This is a straightforward introduction to his critique, not a rhetorical trick. He's about to elaborate on his 'nitpicks,' which is a fair way to structure an opinion.

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.”

Complains about '2028' download speeds — a future problem for a future OS. 💀 — Just Vibes (50/100)

At 28:40

He's talking about 2028 like it's already here. That's not a critique, that's a time traveler's complaint. 😈

Why this score: The speaker is critiquing a current software feature (or lack thereof) by projecting its performance into the year 2028. It's a comedic exaggeration, not a factual claim about current performance, making it 'just vibes' rather than a verifiable statement. The community comments also pick up on this, noting 'it’s 2028 got me bro'.

Original quote: “not having parallel downloads in 2028 is noticeably slower”

Turns a missing feature into a 'signal' of maintainer priorities — pure speculation. 🚩 — Confidence Mismatch (45/100)

At 29:00

One missing feature and he's reading the maintainers' minds. That's not a 'signal,' that's a guess wearing a trench coat. 😈

Why this score: The speaker extrapolates from a single missing feature (parallel downloads) to a definitive statement about the maintainers' priorities ('it's not a priority for the maintainers'). This is a leap of logic, presenting a personal interpretation as a clear 'signal' without any direct evidence of the maintainers' actual priorities or reasons for the feature's absence.

Original quote: “The main problem about this is not necessarily the benchmarks, but it's about the signal. Not having this feature in the package manager signals to me that it's not a priority for the maintainers.”

Claims 'political reasons' for a package rejection — without a shred of evidence. 💀 — Anonymous Authority (45/100)

At 30:00

He says 'political reasons' like he was in the room. That's not a fact, that's a rumor with a confident voice. 🔥

Why this score: The speaker asserts that Void maintainers rejected Hyperland for 'political reasons rather than technical reasons.' This is a significant claim about the motivations of a development team, but no evidence or source is provided to back up this specific accusation of 'political reasons.' Without naming who said it or where this information comes from, it remains an unsubstantiated claim.

Original quote: “the Void maintainers rejected Hyperland from being merged into their package repos for political reasons rather than technical reasons.”

Void devs are 'genuinely really working hard' — a subjective compliment. — Just Vibes (50/100)

At 30:35

He's praising the Void devs, which is nice, but 'really working hard' is just a feeling, not a metric. 💀

Why this score: This is a subjective compliment about the effort and quality of work from the Void Linux developers. While it's a positive sentiment, it's not a factual claim that can be objectively verified or disproven. It's an expression of appreciation, falling into the 'Just Vibes' category.

Original quote: “reason [16:42] given. It's really hard to maintain open [16:44] source software and the Void devs are [16:47] genuinely really working hard and doing [16:49] really great work.”

Void is 'just Arch without systemd and with optional musl and less packages' — a reductive comparison. — False Equivalence (20/100)

At 31:00

Calling Void 'just Arch without systemd' is like calling a demon 'just an angel without wings.' It misses the entire point of the underlying philosophy. 🔥

Why this score: The speaker is simplifying Void Linux by reducing it to a mere variation of Arch Linux. While there are similarities (rolling release, user-centric), Void's design choices, particularly its runit init system and musl libc option, represent a significantly different architectural philosophy than Arch's systemd-centric approach. This comparison downplays the distinct technical merits and design goals of Void, creating a false equivalence that misrepresents its identity.

Original quote: “friendly to the operator, Void is [16:55] kind [16:55] of just Arch without systemd and with [16:58] optional musl and less packages, so it [17:00] belongs in mid-tier for me. Sorry Utox [17:03] and sorry Jake. All right, moving on to [17:05] Linux from scratch. [17:08] Meh. [17:09] Honestly, it…”

His LFS video took 17 hours to record, condensed to 3.5 hours — a personal anecdote. — Personal Story (60/100)

At 32:00

He's just telling us about his own video production. It's his experience, not a universal claim. 😈

Why this score: The speaker is recounting his personal experience with creating a tutorial video for Linux From Scratch. This is a direct personal testimony about his own effort and process, not a claim about LFS itself that requires external verification. It serves to illustrate the time commitment involved in learning LFS, from his perspective.

Original quote: “The LFS [17:21] video [27:00] took me 17 hours [32:20] to record, so I [17:24] had to condense 17 hours of footage into [17:26] 3 and 1/2 hours for the tutorial video.”

Complains about setup time, then pivots to unrelated technical choices. That's a classic misdirection. 😈 — False Equivalence (20/100)

At 32:40

He's equating setup time with core system components. One is effort, the other is architecture. Not the same damn thing. 💀

Why this score: The speaker links the '17 hours to set up' (which is about effort and complexity) to being 'locked into systemd or sysv and GCC and glibc' (which are fundamental design choices of a distro). These are not equivalent problems. A long setup time doesn't inherently mean the underlying components are bad or 'unfriendly'; it means the build process is involved. He's trying to make a technical choice sound like an inconvenience.

Original quote: “talking about 17 hours to [17:36] set this up, sometimes longer, and we [17:38] want operator friendliness, why are we [17:40] locked into systemd or sysv and [music] [17:43] GCC and glibc?”

Calls it 'daily drivable, technically' then immediately contradicts himself. That's a volume game. 💀 — Volume Game (45/100)

At 33:00

He gives it a 'technically' positive, then slams it with a 'no' in the same breath. The retraction is always quieter than the claim. 😈

Why this score: The speaker states LFS is 'daily drivable, technically,' which is a positive, but then immediately follows with a strong 'no, it's not even close to operator friendly.' This is a volume game: a quiet, qualified positive statement followed by a loud, definitive negative, effectively negating the positive without truly retracting it. It's designed to leave the negative impression while technically having acknowledged the other side.

Original quote: “And it's [17:53] an excellent hobby, and it is daily [17:55] drivable, technically, but [music] no, [17:58] it's not even close to operator [17:59] friendly.”

Recommends Debian only for 'boomers' running old web servers. That's a straw man wrapped in an ageist jab. 💀 — Straw Man (20/100)

At 33:40

He's reducing Debian's entire user base to 'boomers' running specific, outdated tech. That's not a fair assessment, it's a caricature. 🔥

Why this score: The speaker limits his 'good faith' recommendation of Debian 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.' This is a straw man argument. He's creating a narrow, somewhat derogatory caricature of Debian's use case and user base ('boomers' using specific, older tech) to dismiss its broader utility or appeal. It's an oversimplification designed to make his 'meh' rating seem more justified than it is.

Original quote: “The only reason this isn't going to go [18:24] in slop tier is that I can in good faith [18:27] recommend this [34:00] [28:20] all [18:16] right. Let's move over to Debian here, [18:18] and I'm going to apologize to Drew in [18:20] advance for this, but yeah, this is meh. [18:23] The only reason…”

Calling Debian 'the opposite of stable' and 'beginner friendly' — pure hyperbole. 😈 — Loaded Language (45/100)

At 34:40

He's not just disagreeing, he's declaring it the *opposite* of what it's known for. That's not analysis, that's a tantrum. 💀

Why this score: Debian is widely known for its stability, even if its packages are older. To call it the 'opposite of stable' is an extreme, emotionally charged statement that ignores its core reputation, used to set up his critique. It's not a factual claim, it's a feeling.

Original quote: “God's greatest [29:00] gift to [18:38] the Linux stability community. Debian is [18:40] the opposite of stable and [music] the [18:42] opposite of beginner friendly for me.”

Listing package versions 'behind' as 'unacceptable' for friendliness — ignores Debian's stability focus. 😈 — Missing Context (45/100)

At 35:00

He's complaining about old packages without acknowledging *why* Debian does it. That's not an oversight, that's a choice. 💀

Why this score: Debian's philosophy prioritizes stability and long-term support over bleeding-edge package versions. While his numbers might be accurate for how 'behind' they are, he's omitting the crucial context that this is a *deliberate design choice* for a specific user base. Presenting it as simply 'unacceptable' without this context is misleading.

Original quote: “is behind like [29:20] [18:52] six versions, and Hugo is like 40 [18:54] versions behind. Rust is 10 versions [18:57] behind. This is unacceptable for [18:59] friendliness to the operator. You're [19:01] going to have to compile all of your [19:02] software from scratch anyway if you're [19:04]…”

Declaring Debian 'definitely better than Ubuntu' — a subjective opinion presented as fact. 😈 — Just Vibes (50/100)

At 35:20

He's stating a preference as an objective truth. That's not a fact, that's just his taste. 💅

Why this score: The claim that Debian is 'definitely better than Ubuntu' is a subjective opinion based on personal criteria, not an objective, verifiable fact. While he's entitled to his preference, presenting it as 'definitely better' without further qualification is a common rhetorical move to assert authority over a subjective matter. It's a vibe, not a verifiable claim.

Original quote: “I mean, the list goes down [19:15] forever, but you get the idea. It's [19:17] definitely [35:40] better than Ubuntu, [music] [19:18]”

Slackware is a 'meh' tier because you have to manually hunt libraries 💀 — No Frame (75/100)

At 36:30

Straight facts about the lack of dependency resolution. No tricks here, just technical reality 🛠️

Why this score: He's describing a specific, verifiable technical limitation of the Slackware package management system without adding unnecessary emotional weight.

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

Red Hat is hiding source code behind paywalls, forcing others to rebuild. Loaded language. — Loaded Language (45/100)

At 38:30

Using 'hiding' and 'paywall' to make a corporate shift sound like a heist. 🕵️‍♂️

Why this score: He's framing Red Hat's move to restrict RHEL source access as a betrayal of 'open source' values. It's technically true that access is restricted, but calling it a 'paywall' adds dramatic weight to what is essentially a standard enterprise model shift.

Original quote: “So, the company that built its reputation on open source is now hiding its source behind a paywall or a paying customer portal. And this is why Rocky Linux and AlmaLinux had to completely rebuild how they build their distros in 2023, 2024.”

Switching from Ubuntu/Yum to Debian/Fedora is a simple choice. False equivalence. — False Equivalence (20/100)

At 39:20

Comparing the massive ecosystem shifts of APT vs YUM like it's just a preference. 🤡

Why this score: He equates the massive, complex decision of choosing a distro ecosystem (Ubuntu/Debian vs Fedora) to a simple 'just switch' command. It ignores the massive friction of moving from one entire software stack to another just because you don't like a specific package manager.

Original quote: “Why would you use Canonical slop when Debian exists if you're married to apt? Well, the same question applies. If you're married to yum, just switch over to DNF and use Fedora.”

Guix is a 'GOAT' distro that mimics NixOS. Confidence mismatch. — Confidence Mismatch (45/100)

At 39:40

Calling it the 'GOAT' before even explaining why. Pure hype 🚀

Why this score: He jumps straight to 'GOAT' status for a niche distro like Guix without establishing the technical merit first. It's high-confidence labeling used to manufacture hype for a specialized tool.

Original quote: “Guix is the goat distro that you probably never heard of or never used. It does almost everything NixOS does.”

Nix lang is a niche, isolated tool — using loaded language to gatekeep its complexity 🎭 — Loaded Language (45/100)

At 40:40

Calling it a language 'nobody uses' is just dramatic gatekeeping to justify the learning curve 💀

Why this score: He's using the 'niche but excellent' trope to frame a steep learning curve as an exclusive club. It ignores the massive growth of the Nix ecosystem.

Original quote: “NixOS uses the Nix lang which is a functional DSL that you have to learn and nobody uses outside of the Nix community even though it's an excellent language.”

Personal justification for a specific setup — using an anecdote to bypass technical trade-offs 😈 — Personal Story (60/100)

At 42:00

He's not making a technical argument anymore; he's just talking about his favorite toy 🧸

Why this score: He pivots from comparing architectures to a purely personal preference about his 'favorite machine' to explain why he doesn't use Guix more often.

Original quote: “Well, because I only have one machine I can run the Libre kernel on and it's my favorite machine.”

Explains missing entries via personal experience and 'fork' logic — Personal Story (60/100)

At 42:40

Just gatekeeping his own list with 'I haven't used it' logic 🙄

Why this score: He's framing the absence of certain distros as a matter of personal experience rather than objective quality, which is fair but inherently subjective.

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.”