Skip to content

Instantly share code, notes, and snippets.

@Amit0617

Amit0617/Why Arch?.md

Last active September 1, 2022 12:46
Show Gist options
  • Save Amit0617/e96bffd956404c9f612ec0addca4e64e to your computer and use it in GitHub Desktop.
Save Amit0617/e96bffd956404c9f612ec0addca4e64e to your computer and use it in GitHub Desktop.
Download ZIP
Convince me Why should I use arch?
Raw
Why Arch?.md
  • If you have HDD, there gonna be a drastic difference in boot time.
$ systemd-analyze

Startup finished in 4.026s (kernel) + 47.655s (userspace) = 51.681s
graphical.target reached after 47.654s in userspace.

47 seconds might sound painful but that was around 2 minutes and 5-15 seconds in ubuntu and 10 minutes in Windows :)

  • For some reason, bluetooth never worked for me on ubuntu

    • Arch gives the fine control over hardware, there are good chances you will get the support for your wireless firmwares on AUR.

  • Arch makes you learn more about your system.

  • Aur mostly have the PKGBUILDs for the github repo, I would wanted to clone and install by myself following their installation procedure(and maybe spending time in installing something while I would like to use that thing.) which makes the process easier and time saving because yay (Aur helper) will install it automatically with one command.

  • Arch has wiki(this thing I like the most) where one can find from how to install, to how to configure and even how to debug and solve errors common to face for almost all the major(it is literally a big and more than enough list) softwares. So spending time with arch and continuously learning through already available sources looks a good long term deal, where your experience grows with spending time with it.

  • Arch is rolling release distro, so it becomes a must for you if you are a developer, there are chances you would be working on Nightly builds which are packaged with latest dependencies which are only available on rolling release distros. But you might never need to be concerned about that if you are only web and/or mobile developer.

MYTHS:

1. LTS = stable & Rolling release = unstable

  • LTS - Long term support (not stable), it will be supported if there any vulnerability and/or bug and/or error is faced by users.
  • Rolling releases are not derived from canary or unstable branches, they are simply latest available releases of softwares which will be made available to LTS distributions after a long time.
  • LTS's lag behind because they have to be supported with particular versions for particular frame of time while rolling releases get updated to latest ones as soon as they are released.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment