You must log in or register to comment.
Unpopular opinion, but how about we take Linux seriously? Arch is a solid OS, unlike Ubuntu, but it’s still much more manageable than say Gentoo or LFS. Get off your high horses.
Yeah, the arch installation on my desktop is about a decade old at this point. It was installed on a completely different computer. No issues.
Arch Linux isn’t actually hard to use, just a pain to set up, but still of you want an arch set up but the convenience like anyone else then use a fork of arch. We’re use Cachy mostly cuz we enjoy the plug and play. No hassle no issues. Though think pads are peak.
What has never worked for us was Ubuntu, haven’t tried Debian tho
My machines got borked every time I tried to do a Debian or Fedora dist-upgrade following the official guide, like 4 times total. Rolling updates on Arch require manual intervention once in a blue moon and haven’t broken my system since I got rid of Nvidia
I have Arch (btw) on my laptop which is the tinkering machine that only I use, and a Win10/Linux dual-boot desktop which is the one other people use that I’m not allowed to break. I had Fedora Silverblue on there originally because I figured it would be pretty stable, but it honestly gave me nothing but trouble. I switched that one over to CachyOS and it’s been smooth sailing ever since.
Ubuntu will actively break itself via
snapdat like 2am on a Sunday.Fedora could not do a fully system update on a 1GB VPS because
dnfwould OOM.The dumbest thing I’ve seen Arch do in over a decade of using it is put RabbitMQ in its official repos while also rolling the latest version of Erlang which RabbitMQ doesn’t support.
Same, but with an ancient Nvidia card even…
I will admit that a week ago I unplugged one of my hard drives and the PC booted into emergency recovery mode, and I had to edit fstab via a series of commands to make it work again, but it only took about 5min.
My browser works fine, got it off flathub.
My graphics drivers work better than they did on Windows by a longshot, I used to get BSOD because Windows didn’t like exclusive audio control ever changing. I’m assuming because of constant advancements in things like Vulkan, Wayland, and xWayland.
Debian never worked for me. Something was ALWAYS broken
Debian might be good for servers, but try using it for work other than server-side stuff. Try installing a productivity application, so you’re not 2 years behind with it! Try plugging in new hardware! Now the tables have turned.
I’ve been working and gaming on Debian for the past few years after Ubuntu started getting annoying with snap, don’t really see any issues with it
Only when I installed it on my new work laptop I had to be like 1 month on sid because of hardware compatibility
I’ve used Arch for more than 12 years, never once has it broken down
This is verifiably not true because of the amount of devs that use arch and the fact that the arch wiki exists and there’s an entire set of AUR packages for custom bugfix patches on top of bleeding-edge software.
Debian is too dated with packages if you want to mess with practically anything new, otherwise its okay for something not concerned with new libs. Ubuntu repos are a joke and you will never find all the libs you need without some wacky tacky 3rd party downloads.
I’m just chiming in to not announce which distro I’m using.
-sent from Voyager on Android
Android, ew. Should be a Linux phone
-sent from Boost for Lemmy
I’ve used debian and arch. Only on debian have I discovered my wifi driver wasn’t yet supported. Only on debian have I turned on a server that I’d left off for a bit and abruptly discovered packages and updates no longer worked due to end of support and that I couldn’t run dist-upgrade without them. I’ve had to do more major surgery on apt then I’ve ever done with pacman.
abruptly discovered packages and updates no longer worked
This happens when you’re at least an entire release cycle behind and haven’t updated the archive signing keys. You need to install them, and possibly modify your sources.list to point at archive.debian.org instead. No major surgery required.
Has nix in their profile name and doesn’t use NixOS 🤔 /s
Arch really is the “Linux” of Linux users, complete with non users making shit up about it.
I wonder how many Arch haters have actually used Arch and ever ran into a breaking issue.
In my 8 years of daily driving Arch, I have had 1 ever, and it was only bad bc I didn’t know of BTRFS yet.
That happened 3 years in, and I went on a new distro-hopping spree in between, trying Fedora, NixOS, and others, and they had actual problems. Not “oh an update broke my system and was fixed in a day.”
So now I’ve been back on Arch for more years.
This whole “Arch is always breaking and takes so much maintenance” is a myth. In reality, Arch is the most stable, because it packages everything Vanilla. Everything works the “standard” way. On Debian, things decay, and then some stuff that’s new breaks with some stuff that’s old. On Fedora, there is a Red-Hat tax: configs in weird places, strange scripts, software missing from main repos (COPR sucks btw). On Arch, it’s just “normal” Linux; and that works
Yeah, I’ve noticed there’s this subsection of people that have a completely wrong understanding of what the term “stable” means in the world of distros, and that it often creates as many problems as it solves, particularly on a desktop PC, or even worse, a gaming PC.
And for there record: Stable just means that things don’t change. That doesn’t mean it contains less bugs, is easier to use or is more secure. And on the flip side it doesn’t mean that distros that are not “stable” are necessarily “unstable” in any shape or form.
Well… because of longer testing periods and a lot of stuff never even considered until stale the stable distros indeed have less bugs. The ones that still slip through however will basically not get fixes for years.
On the other hand I have seen a lot of bugs on Arch… but I usually don’t care and just assume (rightfully so in 99% of the cases) that they get fixed within hours.
I wonder how many Arch haters have actually used Arch and ever ran into a breaking issue.
A lot… they install it, screw up because they didn’t bother to read the instructions, then did the usual… a new install.
Those who pass the first basic barrier to just chroot into the system and fix a simple mistake or roll back a package for the few hours it takes to get fixed instead of starting fresh usually stay for a long time…
In fact with the people I know there is a correlation between either “oh, I don’t bother to fix anything and just do a fresh install (that idea is especially persistent in Windows users)” or “there’s a big distro upgrade that had issues” and distro hopping. Once you settled on a rolling release and learned the basics in terms of fixing stuff the urge to hop yet another time vanishes for many.
“oh, I don’t bother to fix anything and just do a fresh install (that idea is especially persistent in Windows users)”
In fairness, not everyone who did that was just trying to avoid looking into things and learning the correct way. I can’t be the only one who had Arch on a system before getting a smartphone, so early days, that was my sole means of accessing the internet, so if it went down hard and I didn’t immediately understand enough of the error message to at least have an idea of man pages to give a read, I didn’t really have a whole heck of a lot else available to continue trouble shooting. These days, worst case, I can turn on my laptop or grab my phone and search things until I understand the issue and find a solution.
That said, nearly all of my system breaking issues were self-inflicted by trying to do things I didn’t fully understand, just because I thought the end result sounded cool, or not checking the news and unwittingly doing the exact thing the latest post was warning people to be aware of and not do with some sort of major upgrade/change in the base system.
Interesting, my two friends with Arch keep breaking their system 😅 They say its not their fault though!
Debian decays? Can’t relate, I’ve often been running Debian releases until they almost fell out of support (happens on servers) and they were always rock solid after I set them up. It’s only ever an issue if you want to run new software versions without some kind of virtual environment, and generally I just don’t care about that.
I think you can get problems once you are a full release cycle behind the last supported one.
Funnily enough it’s mostly an issue with mirrors and signing keys, so basically the same fix Arch users need if they are behind for many months: update the packages for keys and mirrors first, everyting else afterwards.
This mirrors my experience. I -Syu on a weekly basis, spend about 3 minutes doing pacnews, and then I’m done.
I’m not one of those Arch evangelicals, but this isn’t true at all now.
100%. I’ve got servers running arch for the past 5 years or so and they’re the most stable systems I’ve got. I got so tired of the painful upgrade paths on “stable” distros so decided to switch a server to a rolling release.
After I found arch got security patches into the repos faster than the stable distros could backport, I decided to switch them all over.
I’m even a mad man and have them self update with a script that checks informant (or something, can’t actually remember) for installed packages against news. If no installed packages are found in news, it continues with the scheduled update.
It’s glorious.
I was too lazy for scripting the update to check the news and just get a mail when the update has issues… or should get one.
In reality I check if the email process still works once every blue moon because I didn’t get one from a failed update in years.
I fully endorse gentoo and arch in prod
But it says this screenshot post happened 4h ago.
Did the internet lie to me?
It still says 4h ago. I checked a while ago, still the same. What the heck? Is it moving in time? Always four hours away? How is this possible?!
There might be a bug in your time, check the logs
Ask fusion researchers, they’ve been maintaining a 30 year difference for decades.
Sincerely, a Gentoo user.
