Gentoo goes Binary
Gentoo Linux’s move to offer official binary packages is prompting reflection on what has long made the source-based distro appealing: deep customization, USE flags, and Portage’s powerful packaging model, more than raw performance gains from compiling everything. Many recall Gentoo as an educational rite of passage that taught them how Linux works but was too time- and CPU-intensive to keep using daily, especially as hardware and binary-centric distros improved. Commenters see the new binary repos—especially for common amd64/arm64 profiles—as a way to make Gentoo more accessible and practical, while still preserving the option to compile or heavily customize where it matters.
Overall reaction to Gentoo “going binary”
- Many see this as Gentoo finally adding a missing quality‑of‑life feature: fast installs and updates for common setups.
- Others argue binary support existed for years (stage3, some -bin packages, internal binrepos); the change is scale and official mirrors, esp. for amd64/arm64.
- Some think it’s “15 years too late” for mass adoption; others say Gentoo is healthy as a niche and this just broadens options.
Source vs binary, performance, and learning
- Several report that CPU‑specific build flags rarely give measurable speedups; benchmarks often fall within noise.
- The real gains often came from trimming features and dependencies (via USE flags), not micro‑optimizing CFLAGS.
- Many value Gentoo as an educational tool: learning partitioning, bootloaders, init systems, fstab, kernel config, packaging, etc.
- Some say they “learned nothing” because they just followed recipes; others explicitly used the docs to iterate and experiment.
Portage, USE flags, and customization
- Portage and ebuild tooling are repeatedly cited as Gentoo’s main strengths: clear packaging model, good docs, strong support for custom packages and overlays.
- USE flags are praised for allowing fine‑grained feature control (e.g., drop X, readline, plugins, legacy protocols) for performance, simplicity, or security.
- Concern: official binaries only work when USE flags match profile defaults; people who customize heavily expect to keep building from source.
Comparisons to other distros
- Arch is seen as a “Gentoo lite”: rolling, customizable, but opinionated (x86‑64, systemd) and heavily reliant on AUR.
- NixOS/Guix are noted as having a similar “binary cache + fallback to source” model, with strong reproducibility.
- Debian/Ubuntu/FreeBSD are mentioned as easier, “fire‑and‑forget” choices for servers and users who don’t want constant tinkering.
Practical usage patterns and trade‑offs
- Some still daily‑drive Gentoo on desktops, servers, laptops, SBCs, even low‑power devices, often combining it with cross‑compilation or chroots.
- Others left due to long compiles, fragile rolling updates, or frequent manual intervention, especially on rarely‑touched “production” systems.
- Energy/cost concerns about repeated compiling are raised, but most respondents see it as negligible compared to gaming, web bloat, or other workloads.