It's an obvious vector for malware, arch by default doesn't come with it, and users have been warned the entire time to check pkgbuild. There's nothing fishy, it's just that arch has enough users to be worth it to hit it.
Nicotine never was the worst thing, health wise at least.
I mean it's a language specifically designed to be easy and quick to learn. Even if you don't work with primarily, you'll find it useful for stuff like cli programs, advanced scripts(instead of python), small services, etc.
It was either failing before grub or wasn't in the list, I can't remember now but I know rollbacks were not a possibility. If I remember correctly I had to reboot once after the install, then update, and then reboot once again to have the updated system boot.
This issue can happen with any distro, though rare.
I've used Linux for about 15 years, and that was the only time a fresh install crapped out on me.
Fedora is great, but it's also the only distro I've had fail to boot after a fresh install and update.
Mint for sure. The slower release cycle is definitely better for nontechnical people, but show them how to install flatpaks from the app store.
Damn, the last time I used it I could've sworn it was just arch with a wizard and some custom dotfiles. Although that was like 3 years ago.
I never actually used archinstall, only manual and derivatives which were essentially arch with a wizard.
You can choose the de by clicking in the wizard
how to install arch (with btrfs and without frustration)
Download Endeavour and click through the wizard?
/facepalm moment for not thinking of that at the time
But it's lacking organisation and modularity. For example let's say you need programming packages on one device, gaming ones on another, and general ones on both. It's pretty easy to set it up with hm, and you can disable specific modules when you don't need them (for example you rarely need to use a certain language and supporting packages).
It's pretty fast, especially if you don't get into flakes right away. You basically just install nix with a one liner -> install home-manager through nix -> start adding packages to list.
Here's a comment I made when I was starting out with basic instructions. Do note I'm now using this command for updates instead (updates hm, package definitions, and the packages themselves)
cd ~/dotfiles/nix/ && nix flake update && nix-channel --update && home-manager switch --flake ~/dotfiles/nix/
For me the config management aspect of home-manager is mostly useless. It takes a lot more work to set it up, looks far uglier, and you need to maintain it because parameters change over time. Saving dotfiles in a repo, and symlinking them on install is simply easier.
The only two scenarios where it's actually useful is when you have slightly different configs for different devices, and when the program doesn't support dotfiles. A pretty cool example I've seen for the second one is managing Firefox customisations (settings, plugins, additional CSS), but I'm only disabling horizontal tabs so it's not worth it for me.