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)
I’m not completely up to speed with the core principles of Arch, but I think it revolves around KISS (Keep It Simple, Stupid!). Meaning that Arch doesn’t hold your hand with nice GUIs. Instead, it tries to make the command line interface as easy to understand and use as possible. So if you run into a problem, you’re more likely to understand how to fix it, or at least what the root cause is. Which is not a given when you’re used to distros with more abstraction like Ubuntu. Then again, this design concept is not for everyone.
I don’t think arch does much to make commandline easier to use it understand - instead I’d say it aims to teach you how to use it, because it might be easier than you realize, but importantly it tries to tell you why. Instead of just giving you the command to run, the wiki explains various details of software, and the manual installation process tells you which components you need without forcing a specific choice. As a result, hopefully after using arch you’ll know how your system works, how to tweak it, and how to fix issues - not necessarily by knowing how to fix each individual issue, but by understanding what parts of your system are responsible and where to look.
is the basic arch CLI commands any different from discord bots? it feels easier to use if you think its same as playing with a discord bot. using CLI isnt some kind of programming
They’re a liiittle harder but yeah basically
Thanks for the hearty chuckle, zoomer.
Bash and all other shell languages are programming languages. The terminal is just a REPL for a language primarily meant to be used as a REPL for managing your OS.
learning CLI commands is 10 times easier than HTML
If you’re mindlessly pasting commands, sure… but you have zero idea what your fucking with if you think bash is simpler than HTML.
In the context of maintaining an Arch distro you will absolutely need to understand that executing CLI commands is in fact programming.
hard disagree on this… while for people who don’t know it it might look like programming, it’s really not much different than editing config files (which people who don’t know it will assume is programming too).
Sure, the language used by bash can be used to write massive programs. But in 99% cases using the CLI is like using a gui with a button and a text field - type some text into the field and then click the button, letting whatever software you’re running take the content of the text field and do something with it.
way closer, in fact, to executing a discord bot command, than to actual programming as in software development (what i’d argue people think of when talking about programming)
If you even write one line of bash you are programming. The way you’re describing it only makes sense if you’re using the terminal like
dmenu_run. You metaphor breaks down the moment someone so much as usescd. Even worse once you throw a pipe or redirect in. All of this you absolutely will have to do when installing Arch.Its absolutely irresponsible to tell people that installing and running Arch Linux is like talking to a discord bot.