Using Arch without a bigger org managing it for you is kind of dangerous. Their policy is that they just wantonly push anything, and if there’s something wrong with a package they’ll tell you in the upgrade message. That you’ll have to manually evoke. And check for each package upgrade.
I learned a lot from setting up Arch a couple of times, but ultimately I think they have a few policies that are terrible for the average user or even company.
I work in Deep Learning, and the NVIDIA version comes in really handy.
I never face NVIDIA issues like my peers frequently complain.
Special optimizations? How? Compile the world like Gentoo so as to use every single instruction of your CPU? Cool, I can actually stand behind that and install the OS because of it.
But what does "a hardened Linux kernel" mean?
I feel that that page expects you to know a lot about CachyOS already and I found myself impatiently closing the browser tab when I was about 50% in.
Are there better introduction articles?
Basically they package many kernels with different schedulers, hardening and such to choose from. I believe hardened linux may even be a vanilla Arch kernel?
And its not like Gentoo, they run their own repos like Clear Linux or ALHP were everything is basically built for Haswell and up (and very soon AVX512 CPUs like rocket lake/zen4). But unlike Manjaro, the vanilla Arch repos are also used, and are the system target.
Other than that... Its more or less an Arch installer, like EndeavorOS. Perhaps that is why it doesn't need an introduction, because beyond some qol it is Arch Linux. Thats kinda the point.
Which is both good, and actually sane.
NixOS: Exists. (And runs great after I moved from Arch 1.5 years ago!)
I found this to be 100% correct. You feel like you won’t ever need to distro-hop again, right? Like this is the penultimate Linux distro? Right?
Since NixOS's rough edges can be quite rough, perhaps 'penultimate' may be more apt. (I mean, when NixOS works well, then it is amazing; but if you hit some use case where NixOS is difficult to use, then it requires more effort/understanding to get through).
1. Use flakes to set up your system and do work with. It sometimes feels underdocumented, but it's worth some headscratching imo.
2. Don't worry about putting everything in the base system. Stick to services (Tailscale, Syncthing, etc) and system/base desktop software. It's easy enough to use nix run, or Podman, or flatpak, or even AppImage to a degree.
3. Want to configure something declaratively? Before pulling out HomeManager or another user tool, consider configuring software at the system level. I do this for Zsh, SwayWM, etc. As a bonus, you can easily block off shell startup files and chown them to root so that malware can't trivially insert themselves there. (It's a weak protection, but definitely doesn't hurt in addition to other approaches.)
There's more (I recommend using Nix-ld to support AppImage and raw binaries better) but these things go a long way.
Nix is basically the future of operating systems. The one problem that still needs solving, which is blocking wider adoption, is ease of use. People are working on making the command line tools easier, but what will really do it is something that abstracts away config generation with a UI installer and tools, but opens up the config if you go into "advanced mode" or something like that.
Helps to get some intuition on what fits where.
Surely, hammer is fast enough to render retro indie games at 60fps. :-)
I don't want to babysit my computers. My wife would also not be amused
The only thing with arch that is blocking a non-techy/fiddle-unfriendly person is the installation process (even with the script, knowing what a DE is, making a conscious decision which to choose, KDE etc)
I think your definition of "non-techy/fiddle-unfriendly" is quite different from the rest of the population.
Also note, that just because you happened to had months of no problems, that does not mean it will be the same experience for someone else. Speaking of it: for a non-techy person, using the terminal is already a problem.
What OS is she using now?
As a young teenager I got the bright idea to get my mother using Linux. Later I bought her a Mac and she was much happier. Wish I'd thought of that sooner.
(I have no particular attachment to any OS (hate them all equally ;), it's mostly a matter of what you're used to, and picking the right tool for the job.)
I then switched to Ubuntu and then to Manjaro and had only one break (it just wouldn't boot, but I easily found instructions on how to fix that) in many years straight.
I don't say Arch is bad but to me it seems like it is rather far from perfect while Manjaro is the closest to perfect I have ever seen.
Needless to say I appreciate Arch exists and am very grateful for the amazing job they do. Obviously no Manjaro would exist without Arch in the first place. Arch Wiki deserves a separate mention as it is of great quality and often helps a lot no matter what actual distro are you tweaking (it helped me with Ubuntu).
I found reading the installation guide intimidating!
It is worth doing at least once, it teaches you a lot about Linux.
I used to recommend Manjaro to people as an alternative to Arch that's a bit friendlier, but I stopped after trying to debug an issue and realizing that they have overcomplicated a lot of things (kernel management in particular bugs me in Manjaro.)
Arch now has some kind of installer, so I guess that's an improvement. Though, I really wish Valve could package something like SteamOS 3 for regular desktops. I'm aware of multiple projects that do similar things, but the execution on Deck is quite good. The "immutable" concept is certainly going to be an important part of Linux on desktops in the future, probably in different forms.
[1]: https://manjarno.snorlax.sh/