Linux

63165 readers

645 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

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

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

founded 6 years ago

MODERATORS

AgreeableLandscape@lemmy.ml

nooter692@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

Why go through the trouble to use Arch? (lemmy.world)

submitted 3 months ago by Horsey@lemmy.world to c/linux@lemmy.ml

125 comments fedilink hide all child comments

May be a mean sounding question, but I’m genuinely wondering why people would choose Arch/Endevour/whatever (NOT on steam hardware) over another all-in-one distro related to Fedora or Ubuntu. Is it shown that there are significant performance benefits to installing daemons and utilities à la carte? Is there something else I’m missing? Is it because arch users are enthusiasts that enjoy trying to optimize their system?

you are viewing a single comment's thread
view the rest of the comments

[–] just_another_person@lemmy.world 8 points 3 months ago* (last edited 3 months ago)

It's not "trouble" if you're already familiar with Linux. It's not the way I would go as a user of 20+ years, but it's not just for desktop use.

If you're looking to build a platform for something, it's perfect. Look at why Valve switched to use to for SteamOS. You have an underlying framework of a stable system, and you just create automation to slap it all together into the base layer of all the things you want without having to worry about specific things breaking the stack you're building on top of it.

It's like a blank page instead of a notebook with line guides.

It helps make more sense if you think of everything you've got to build on it already existing in a git repo. Merge > Build > Release. Makes perfect sense, and you save yourself creating an entire distro to maintain from scratch.