this post was submitted on 17 Feb 2025
562 points (84.4% liked)

Linux

50381 readers
1353 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago
MODERATORS
 

Arch is aimed at people who know their shit so they can build their own distro based on how they imagine their distro to be. It is not a good distro for beginners and non power users, no matter how often you try to make your own repository, and how many GUI installers you make for it. There's a good reason why there is no GUI installer in arch (aside from being able to load it into ram). That being that to use Arch, you need to have a basic understanding of the terminal. It is in no way hard to boot arch and type in archinstall. However, if you don't even know how to do that, your experience in whatever distro, no matter how arch based it is or not, will only last until you have a dependency error or some utter and total Arch bullshit® happens on your system and you have to run to the forums because you don't understand how a wiki works.

You want a bleeding edge distro? Use goddamn Opensuse Tumbleweed for all I care, it is on par with arch, and it has none of the arch stuff.

You have this one package that is only available on arch repos? Use goddamn flatpak and stop crying about flatpak being bloated, you probably don't even know what bloat means if you can't set up arch. And no, it dosent run worse. Those 0,0001 seconds don't matter.

You really want arch so you can be cool? Read the goddamn 50 page install guide and set it up, then we'll talk about those arch forks.

(Also, most arch forks that don't use arch repos break the aur, so you don't even have the one thing you want from arch)

you are viewing a single comment's thread
view the rest of the comments
[–] independantiste@sh.itjust.works 20 points 4 days ago (3 children)

The level of disillusion in the thread is insane. At no point in time is it a good idea to recommend Arch and it's derivatives to Linux newbies. They will 100% wreck their install in the first two weeks. Even I, as a pretty experienced user had to wipe my arch install after failed update attempts, luckily I had a separate home partition. Anything else like fedora or tumbleweed will provide packages that are very up to date, but that are also tested. For example I don't fear that updating my fedora install will completely brick the networking of my system like what happened to me on arch.

Ironically I wouldn't recommend any Ubuntu derivatives as for some reason, every single time I've installed Ubuntu or one of its variants like PopOS they ended up messed up in some way or another, albeit never as critical as Arch did to me numerous times. Probably some kind of PPA issues that make the system weird because it's always the fault of PPAs

[–] Endymion_Mallorn@kbin.melroy.org 8 points 4 days ago (1 children)

Mint has worked consistently for me on the PC it's installed on.

[–] accideath@lemmy.world 7 points 4 days ago

Second this. Am not a huge fan of ubuntu itself and I have had issues with other debian based distros (OMV for example) but mint has always been rock solid and stable on any of my machines. The ultimate beginners distro imo.

[–] 0x0@programming.dev 6 points 4 days ago (1 children)

Ubuntu or one of its variants

Even Mint? Seems to be the go-to recommendation for newbies.

Never was able to try mint, I only did once but the installer didn't work for some reason, probably Nvidia related so I don't blame mint for it.

[–] Allero@lemmy.today 1 points 4 days ago (1 children)

Honestly, as someone who ran Arch and its derivatives, no one should be running upstream Arch but the testers.

No amount of experience or expertise will save you from breaking it. It WILL break, and you'll be mocked for that as well by "Arch elitists" who will then face the same issue.

That's why Linux veterans are rarely using Arch. It's good for its purpose, it's very important both for downstream Arch and for the entire Linux community, but it is NOT the distro you should run on your PC.

Go Fedora. Go Debian. Go to the downstream distros if you're strongly into Arch, take Garuda for example. Make your machine actually work.

[–] CarbonBasedNPU@lemm.ee 7 points 4 days ago (1 children)

What do you define as breaking? I ran arch and cachy and never once had a breaking issue.

[–] Allero@lemmy.today 6 points 4 days ago (2 children)

Some functionality (menus, networking) working not as expected, random glitches, bugs, instabilities...also, now coming from the experiences of others (wasn't there at the time), one time even GRUB had an update that broke it on all systems with Arch, forcing many to halt updates. In my eyes, from personal experience and experiences of others, it got a reputation as a quite messy system.

[–] Aatube@kbin.melroy.org 2 points 3 days ago

The GRUB update is why more Arch needs more testers lol. They do have separate repositories for testing, but none of the active testers had the relevant problematic configuration that caused that problem during the testing period, and then it shipped to stable. The package maintainer did configure the package to not include the breaking change that same day, but it doesn't look like that was ever shipped for some reason.

[–] independantiste@sh.itjust.works 2 points 4 days ago (1 children)

Oh wow yeah I had forgotten about the grub update, the only way to not have a bricked computer was to be active in the arch communities because they didn't remove the faulty package even though it was known to brick computers