▶ YouTube Summaries

• https://www.youtube.com/watch?v=9kxx5xp5nTQ
• Original title: "We will ruin your life" -Microsoft

On "The Stand-Up," guest Trash recounts his two-week, "hell on earth" journey switching from a 10-year-old MacBook Air to Linux, hopping through Fedora, Debian, Pop!_OS and more. The crew dissects why Linux is hard for newcomers, the Hyprland/Wayland/compositor stack, hardware advice, and the deeper reason Linux can't ship binaries reliably. The clickbait "Microsoft" title refers only to a running gag that the one truly stable, write-once-run-everywhere substrate on Linux today is ironically the Win32 API (via Wine/Proton).

The Linux conversion arc

• Trash wiped macOS off an ancient (~2015) MacBook Air and spent a brutal first week just getting a distro to boot; distro-hopped (Fedora first) on Twitter advice.
• Hand-wrote most config the "pre-AI" way (Stack Overflow, reading dotfiles), leaning on ChatGPT only when fully stuck.
• Now "Linux pilled" and addicted to customization; plans a new machine, Arch and NixOS, gaming, and moving his work machine over. Repo: github.com/bautistaaa/dotfiles.

Desktop stack: Hyprland, Wayland, compositors

• Wayland is a protocol/spec; a compositor (e.g. Hyprland) implements it. Hyprland bundles tiling WM + compositor in one, versus stitching things under i3.
• Tangents on per-app config, terminal opacity/blur limits set by the compositor, and "Wallust" (Rust tool that re-themes the desktop from the wallpaper's colors).

Hardware and distro advice

• Avoid discrete Nvidia GPUs on Linux; prefer AMD or Intel integrated. Exception: System76 or Framework that design/test for Linux.
• AMD "just works"; Nvidia hit-or-miss. Praise for Framework and System76; a negative Lenovo customer-service anecdote. Out-of-box install reliability and the package manager are the main real differentiators between distros.
• Battery-life praise for a sponsor-supplied Dell XPS.

The core gripe: Linux can't ship binaries

• Casey's critique: Linux has never produced a stable userland ABI for "write once, run as a binary everywhere." Kernel API is stable; userland is fragmented.
• Workarounds all amount to containerization: AppImage, Flatpak, Snap, Docker - each bundles its own userland deps, breaking shared config and never fully integrating.
• This fragmentation is also a feature: it enabled diverse distros (Pop!_OS, Mint, NixOS, Omarchy/DHH, Bazzite) to experiment with userland.
• For out-of-date packages: add the upstream project's repo, or build from source / use an AppImage.

Punchline: the only stable substrates

• The two substrates that have persisted are Win32 and the browser. A sane Win32 64-bit binary now runs on "all Linuxes" via Wine/Proton; macOS is also bad at stable binaries (notarization friction).
• The most reliable way to ship a stable Linux binary is to write a Win32 app and let Proton handle it. Web apps make the binary problem moot for many users.