Arch is only the larval stage. When a Linuxite consumes enough CLI, they metamorphose into one of two adult forms: a Void user, or a NixOS user. As these two adult forms are incompatible, this is a rare case of species divergence within a life cycle. Even more oddly, like the axolotl, many Arch users never leave the larval stage, and continue living comfortably in their ecological niche.
Yeah, that comment leaves out the "I learned a lot from Arch, but don't have the time to manage evertything anymore" crowd, which goes Ubuntu -> Arch -> Debian/Mint/Fedora
I discovered that EndeavourOS satisfied that for me, without me having to give up Arch. And snapper+btrfs-grub has eliminated any interest in messing about with the new line of immutable systems. The only tempting distro I might spend time in is Chimera Linux (link, b/c of an unfortunate naming conflict) which (a little hilariously) is an attempt to make a Linux distro that's purely Gnu-free. Chimera also runs dinit instead of systemd, and that's interesting.
Anyway, there are a couple of options that let a user stay in Arch but make things less... fussy.
Yeah, it is a lot of initial work, but once you got your shell.nix or flake.nix in place it is really nice, to not have to deal with different dependencies and versions in different projects.
But you can also archive the same on any distro with the nix package manager.
It's an investment for the next time you install on a new dev machine. After install, I will literally run a single command to return to the exact state of my dev environment.
Probably not often, but as a Debian user, it's a PITA to get back to where I was before I fucked up my system. Nix(OS) sounds like a future investment to me, just in case I ever fuck up and need to get back to where I was ASAP. Been there once already and it was NOT fun.
That was from a professional standpoint BTW, privately I'm still a dirty Windows pleb, because that's what I'm most familiar with.
PS: I'm already using a dotfiles repo, which already saves me a ton of time in settings things up.
This is why I run Manjaro, which I never hear any love for here for some reason. It's the rolling releases and cutting edge updates of Arch, but with the ease of use and reliability of Debian. Insert a bootable USB and have a fully functional system in a couple minutes.
Manjaro just works, from gaming to development, and I've never been forced to play games to install a hardware driver or newer library that isn't part of the release like with Debian or Ubuntu.
Been using Linux for over 20 years and never seen a distro so trouble free.
The reason you don't see a lot of love for Manjaro is because your experience isn't quite typical. Manjaro is notorious for taking Arch and making it less stable. It's mostly Arch with some defaults and software to make it easier to set up, but the few cases where it drifts from Arch tend to cause more issues than if you just used Arch directly.
Interesting, I've installed it on quite a few machines now, all with widely varying hardware. Aside from my development/gaming rig I've got a shop laptop which is used by various goons to view shop drawings and look up parts, one the ex-wife still hasn't managed to break, one is my 9 year old daughter's and another is a potato that runs my 3d printer (to be fair this one is fossilized and doesn't get updates).
All are working great with no setup effort and no maintenance so I guess it's a classic case of YMMV. I wouldn't have used Arch for any of those use cases except maybe the 3d printer.
Agreed, i had more issues on Manjaro than i ever did on raw Arch. The Manjaro team, at least during the time i used it, didnt seem very good at keeping things working. So many issues with bad packages, keys expiring, stuff like that.