Bazzite Post-Mortem

Framing of “Post-Mortem”

  • Several commenters object to calling it a “post‑mortem” because Bazzite is still active; they find it misleading and somewhat petty.
  • Others argue “post‑mortem” is commonly used in tech as “incident report” or retrospective on a finished event, not necessarily the end of a project.
  • Consensus: the title is at least confusing; some see it as personal drama framed as project death.

State of the Bazzite Project

  • Multiple people stress that Bazzite is not dead and continues to grow; it’s built as a “mod” of Fedora Atomic, so the technical base is solid and replaceable.
  • There is disagreement over how central the departing developer was: some say they did most low‑level hardware work, others counter that their code can and will be replaced.
  • Some users now see Bazzite as less stable or “politically toxic” and plan to migrate (often to CachyOS or Fedora Kinoite), while others remain happy users and plan to stay.

User Experiences and Technical Value

  • Positive reports: “it just works” for gaming, especially on Nvidia and handheld/odd hardware; easy Secure Boot + Nvidia driver setup; good defaults for immutable/container workflows; easy rebase to/from Fedora Atomic.
  • Negative reports: crashes in Bazaar (the app store), fast‑moving kernel/hardware changes breaking external utilities, odd UX decisions (e.g., questionable options in Bazaar, slow terminal exit).
  • Some users were alarmed by the headline because they had no prior indication of trouble.

Alternatives and Distro Philosophy

  • Many recommend more established or company‑backed distros (Fedora, Debian/Ubuntu, Arch) for long‑term stability; specialized “gaming” distros are seen as convenient but fragile.
  • Alternatives mentioned: CachyOS, Nobara, Jovian NixOS, Fedora Kinoite/Silverblue, EndeavourOS, Linux Mint, SteamOS.
  • There’s a long tangent on Mint (praised for stability, criticized as outdated/X11‑bound) and on fragmentation of package formats (apt/dpkg, rpm, Flatpak, Snap, AppImage).

Governance, Conduct, and Drama

  • Official Bazzite line (per commenters): the removed developer violated the Code of Conduct and harassed people on Discord; others downplay this as “mean words,” leading to a debate about what constitutes harassment and when removal is justified.
  • Some see the blog post as an immature, one‑sided attempt to portray themselves as a victim; others think both sides share blame.
  • One commenter offers a conspiratorial theory about Microsoft influence; others explicitly label this as unevidenced.

Discord and Community Dynamics

  • Several blame Discord‑centric communities for fueling drama and excluding non‑users; they prefer searchable, open archives (forums, IRC, Matrix, etc.).
  • Others note that chat drama predates Discord; real‑time social spaces always risk conflict but also enable mentorship and enthusiasm.