Back to FreeBSD: Part 1

Original Article ↗ Hacker News Discussion ↗

FreeBSD vs Linux design and culture

  • Several commenters praise FreeBSD’s “engineering, not hacking” mentality, consistency of tools, and conservative, planned changes versus Linux’s more ad‑hoc evolution.
  • Others argue Linux’s messiness is simply the byproduct of success and scale; if BSD had won, it would have acquired similar layers of abstraction.
  • Some note FreeBSD userland feels more homogeneous and coherent (e.g., consistent signal handling, ifconfig semantics), while Linux tools vary strongly by author and distro.

Jails vs containers / Docker

  • Many push back on equating jails with Docker: Docker’s win is attributed to ecosystem and UX (Dockerfiles, registries, compose, one‑liner deploys), not the isolation primitives.
  • Jails are seen as technically elegant but lacking a native shipping/registry story and high‑level tooling (compose‑like orchestration, “Jail Hub”).
  • Some mention BastilleBSD and newer OCI/podman support as steps toward Docker‑like workflows, but note emulated Linux containers on FreeBSD feel “half‑baked.”
  • Debate over simplicity: some say spinning up Linux containers is easier; others insist a basic jail is just a few lines of config and highlight VNET jails and ZFS delegation as strengths.

Ecosystem, momentum, and hardware support

  • Multiple comments attribute Linux’s dominance to early driver support, commercial backing, and familiarity, creating a self‑reinforcing “momentum” BSD never caught.
  • Historical shortcomings: FreeBSD lagged on SMP/threading and still lacks drivers for many modern devices, CUDA, and HPC fabrics, making it a non‑starter for supercomputers and AI clusters.
  • Counterpoint: Linux’s ubiquity doesn’t prove its philosophy is better, just that it aligned with who had resources and needs at the time.

Packaging, upgrades, and “coherent OS” claims

  • FreeBSD’s clean base vs ports separation, ZFS on root, and reliable in‑place upgrades across multiple major releases are frequently cited as major practical advantages over Linux distros like CentOS/Rocky.
  • Others argue FreeBSD is still “just another curated soup of upstreams,” much like Debian, and that Linux packaging ecosystems are at least as sophisticated (Nix, ostree, Flatpak, etc.).
  • One thread disputes the idea BSD packaging is uniquely safe; Linux users note immutable and modern packaging approaches reduce “bricking” risk similarly.

Personal usage patterns and frustrations

  • Several longtime FreeBSD users describe migrating whole companies or startups to it for “quiet, boring, stable” servers, while often keeping Linux on desktops for broader software support.
  • Others recount starting on BSD or Linux in the 1990s and ultimately sticking with Linux simply because it already did everything they needed.
  • Some express fatigue with Linux’s politics (Xorg drama, corporate agendas) and disruptive changes like systemd‑oomd killing entire cgroups, which push them toward FreeBSD’s slower‑changing, less politicized environment.

Miscellaneous

  • Side discussions cover: Windows vs Unix developer “types,” the difficulty of deeply understanding NT vs Unix, and frustration with web‑application firewalls blocking the article (“failed to verify your browser”).
  • There is interest in deeper technical writeups on how isolation works in containers and VMs; commenters briefly outline that Linux “containers” are user‑space constructs over namespaces, cgroups, and seccomp, not a single kernel feature.