Aeon: OpenSUSE for Lazy Developers
Aeon, an immutable openSUSE-based desktop aimed at “lazy” developers who don’t want to manage their OS, prompts mixed reactions: some praise its automated updates, rollbacks, and container-centric app model, while others find it too opinionated, under-documented, or lacking essentials like an enabled-by-default firewall and polished installer. Commenters frequently compare it to Tumbleweed, Fedora’s Atomic/Silverblue variants, NixOS and traditional distros, weighing the trade‑offs between simplicity, stability, and flexibility, especially around GPU drivers, secure boot, Btrfs performance and software availability. The broader role of SUSE in enterprise, HPC, and everyday developer workflows also surfaces, with many highlighting its testing infrastructure and tooling as reasons to consider it over more mainstream Linux options.
Positioning of Aeon / “Lazy Developers”
- Aeon is seen as an immutable desktop aimed at users who want minimal admin work: automated updates, rollbacks, containerized apps, and a locked-down base system.
- Some are confused by the “for developers” label; it looks similar to a “lazy desktop” for non‑developers.
- Critics say you still need to learn new workflows and packaging models (Flatpak, containers, possibly custom RPMs), and customization options are limited versus what many developers want.
Immutable Model, Apps, and Tooling
- Base system is updated transactionally; rollbacks and btrfs snapshots are central.
- Apps are expected to come via Flatpak or containers (distrobox). Some devs prefer using Guix or Nix on top of Aeon/MicroOS instead of Flatpak/distrobox.
- Concerns: key tools (e.g., Firefox Flatpak on AArch64) and some niche software aren’t always available as vetted Flatpaks, pushing users to “random” sources.
Security: Firewall, Secure Boot, Encryption
- Controversial: Aeon initially shipped without a firewall; maintainers argue an immutable, non‑listening base doesn’t need one and extra services increase attack surface.
- Opponents insist a default “deny incoming” firewall is important because user apps may open ports.
- Some users simply install firewalld via transactional-update despite it being “against the grain.”
- Tumbleweed and Leap are praised for good Secure Boot + Nvidia support, though others recount painful MOK and driver workflows.
- New Tik-based Aeon installer reportedly dropped full‑disk encryption support, blocking adoption for some.
openSUSE Ecosystem & Reputation
- Many commenters run Tumbleweed or Leap as daily drivers (desktops, laptops, HPC, corporate, scientific workloads, NAS-like appliances).
- Tumbleweed is repeatedly described as “Arch‑like but more stable,” with strong automated QA (OBS + openQA), easy rollbacks (snapper + btrfs), and relatively fresh packages.
- Some call openSUSE “niche,” especially outside Europe; others dispute this and argue most major distros are now similarly stable.
Rolling vs Immutable & Btrfs
- Debate over rollbacks: supporters value fast recovery from breakage (especially with 3rd‑party repos); skeptics note rollbacks leave you on old software without fixing root causes.
- Immutable systems requiring reboots for OS updates are seen as a minor tradeoff by some, annoying with full-disk encryption by others.
- Btrfs is standard; concern is raised about poor VM/database performance without
nocow, and advice is to put VMs/DBs on a separate ext4 partition.