It honestly baffles me why people install a distribution explicitly designed for granular, terminal-centric control, only to immediately try and hide it behind a GTK wrapper.
If the goal is to avoid the terminal while managing system packages, AUR builds, Flatpaks, and Snaps all in one place, distributions like Manjaro or Ubuntu already exist for that exact use case. Bolting a two-month-old GUI on top of pacman and yay or paru is just a recipe for a broken system down the line.
When a PKGBUILD fails, a PGP key needs importing, or a manual dependency intervention is required, you need to see the actual terminal output. Hiding those critical prompts behind a shiny interface just obscures the exact information Arch relies on you to manage. If you are trying this hard to avoid the terminal, Arch is probably the wrong tool for you.
It honestly baffles me why people install a distribution explicitly designed for granular, terminal-centric control, only to immediately try and hide it behind a GTK wrapper.
If the goal is to avoid the terminal while managing system packages, AUR builds, Flatpaks, and Snaps all in one place, distributions like Manjaro or Ubuntu already exist for that exact use case. Bolting a two-month-old GUI on top of pacman and yay or paru is just a recipe for a broken system down the line.
When a PKGBUILD fails, a PGP key needs importing, or a manual dependency intervention is required, you need to see the actual terminal output. Hiding those critical prompts behind a shiny interface just obscures the exact information Arch relies on you to manage. If you are trying this hard to avoid the terminal, Arch is probably the wrong tool for you.