Arch has no reason to exist as almost all of it's benefits are replicated with nix without having your system fail to boot because you dared to update it.
I decided to dump arch when I was working in a foreign country for a month, had bad internet, and had to weigh whether -Syu or -S would be more likely to break my system. Shit's way too stressful.
Run pacman -Syu, reboot, and it fails to boot. Had it happen many times with arch and derivatives on multiple devices. It's far more likely to happen if you don't update for like a month.
Also have a copy of pacman-static somewhere so that you can fix your shit in case of a partial upgrade (and trust me, it can go horribly wrong)
And thirdly, Arch is meant as a power user distro -- despite this abhorrent popularity it has gained, the fact of the matter remains that you need to know the system inside and out, if you make your arch system unable to boot..... Don't use arch
This is not my attempt at elitism. Arch was never meant to be a hassle free distro and it sure as shit is not one.
There are many maintenance-free distros you can use instead. Can I offer you a Debian in these trying times?
Also have a copy of pacman-static somewhere so that you can fix your shit in case of a partial upgrade (and trust me, it can go horribly wrong)
Oh I know, I quickly learned to never update it without having live media nearby to arch-chroot with.
if you make your arch system unable to boot..... Don't use arch
The only thing I did to make it unbootable is to update it. Going by that logic nobody should use it.
This is not my attempt at elitism. Arch was never meant to be a hassle free distro and it sure as shit is not one.
I definitely agree, that's why I'm commenting against dumbasses suggesting it to beginners. Especially when they glorify AUR.
Can I offer you a Debian in these trying times?
No need, I already landed on MX + nix after 2+ years of arch. Nix unstable gives me all of the benefits of arch (except for the DE) and then plenty more on top. Different downsides, but far less stressful. I'm
You need to keep the update log and go through the whole thing and see if something needs reconfiguring. Sounds shitty? Yeah, that's why I stopped using Arch and Gentoo despite being a veteran
Nowadays I just install Debian or some derivative and call it a damn day. Unless you need some exotic setup (and those are more suited to Gentoo or Slackware anyway)
Oh I had a far simpler method: update and it fails to boot? Rollback and try updating again in a week. It usually works then, but I had to wait a bit more a couple of times.
The only exception was that bad GRUB release. I think that's the only update fail that absolutely required arch-chroot.
I guess I'm smart enough to install opensuse, but dumb enough that I somehow got slow pacman.
I kid you not, on my hardware zypper is the fastest between ubuntu apt, fedora dnf, and arch pacman. dnf was the second-fastest on my hardware, with apt and pacman being pretty sluggish
I've also used portage which was even slower, but probably not a fair comparison considering how much more complex it is.
In the grand scheme of things the difference between C, C++, and Python isn't meaningful when operating over a network (edit: for a single-user system). It's very likely that the difference for thread OP is just caused by weaker connections to specific repos.
We're talking about a package manager, not a game, network server, etc. On a basic level the package manager only needs to download files from a network and install them (OS syscalls for reading/writing files, these are exposed C functions or assembly routines), or delegate to a specific package's build setup (which will also likely be written in a compiled language)
Arch stable ? I mean, from experience, I've had one break in stability so bad it made me hop : the lack of gentoo-like config protect. To be fair, I was on Artix but the breakage was versions of Pipewire deleting not just my changed config files but config files it couldn't run without ! Or to be fair, also, actual Arch but on my phone, plasma 5 package conflicts (that came as is from the installation image) prevent the whole system from updating 🙃 ... Never had any of those 2 problems on OpenSUSE or, to be fair, non-Arch-based distros
Nevermind : just got my boot borked on OpenSUSE (which is dumb as the rest of the system is fine but I can't easily just reinstall just the boot) THANKS, TPMs
Edit : "what do you think is stable then ?" idk, fcking Gentoo ? "And what if I don't wanna compile blah blah" use linux lite, may not be rolling and pretty nooby but it is stable and the only one I feel comfortable handing to my mom (amongst the ones I've tried) without that much bloat
That sounds reasonable to me! Would explain why the mobile app has it and the web app doesn't; I don't know if a Lemmy instance has a way to advertise the functions it supports to third party apps.
I think blocking downvotes is an option built into Lemmy servers that can be communicated through the API. I know there are a decent amount of instances that don't federate downvotes because of toxicity concerns.
For me, the Boost Lemmy app let me downvote even though my instance has it disabled... It just quietly failed and when I go back the downvote isn't there.
The Jerboa and Voyager apps, on the other hand, don't: Voyager let's you try but correctly shows an error, while Jerboa flat out doesn't offer it since I can't anyway
Problems I had were because of software not being on the latest version, not updates. Things just work on Arch for me. Only thing that ever broke was Xorg because of Nvidia drivers but that's pretty easy fix.
You've been lucky. I've been daily driving EndeavourOS for a few months now and I really love it but it did spontaneously break spectacularly twice already due to updates.
Problems I had were because of software not being on the latest version
I really need to get someone to make a jingle for this: just use flatpak/appimage/distrobox/nix...
Things just work on Arch for me.
And how long have you been using that install? I ran arch and derivatives for 2+ years on multiple devices and can't count how many times they failed to boot due to an update.
MX + nix unstable give me the same bleeding edge packages without risking my system exploding randomly, while also giving me a bunch of other benefits.