I Use Arch BTW: My Setup and Why I Torture Myself

A walkthrough of my Arch Linux setup, or: how I learned to stop worrying and love the terminal

Yes, I’m that person. I use Arch Linux. I will tell you about it. Repeatedly.

But seriously, after a year of daily-driving Arch for development, I’ve got opinions and a setup that (mostly) doesn’t break every update. Let me walk you through it.

Why Arch? (The Actual Reasons)

Look past the memes and superiority complex, and there are legit reasons:

The Good:

  • Rolling release = always bleeding-edge packages (until something breaks)
  • AUR = literally any software exists here
  • Minimal base = you only install what you need
  • Forces you to actually understand your system
  • Did I mention I can say “I use Arch btw”?

The Bad:

  • Updates can and will break things at the worst possible time
  • You WILL spend a Saturday fixing something that worked yesterday
  • Installation is a rite of passage (or torture, depending on perspective)
  • Reading the wiki becomes your new hobby

My Current Setup

The Foundation

After reinstalling Arch approximately 4 times (learning experience™), here’s what stuck:

# Display server: Wayland because it's 2025
# WM: Hyprland (tiling, because I'm pretentious)
# Terminal: Alacritty (GPU-accelerated, so fast)
# Shell: zsh + oh-my-zsh (I know, basic)

Development Environment

This is where I actually spend my time:

# Editor: Neovim
# Why? Because I like suffering and also it's actually great
# Config: ~800 lines of Lua I barely understand

# Terminal multiplexer: tmux
# Because tabs are for quitters

# File manager: ranger + lf
# Sometimes GUI file managers, when I'm feeling lazy

The Tools That Matter

Package Management

# Official repos
sudo pacman -S <package>

# AUR (use yay or paru)
yay -S <whatever-obscure-package>

Pro tip: Always read the PKGBUILD before installing from AUR. Or don’t, and live dangerously.

Development Essentials

# Languages
sudo pacman -S jdk-openjdk python rust go nodejs npm

# Build tools
sudo pacman -S base-devel cmake ninja

# Version control
sudo pacman -S git lazygit  # lazygit is a game-changer

# Docker (because containers)
sudo pacman -S docker docker-compose
sudo systemctl enable docker
sudo usermod -aG docker $USER

My Terminal Setup

Alacritty config highlights:

# Font that makes code look good
font:
  normal:
    family: JetBrainsMono Nerd Font
  size: 11

# Colors: Gruvbox because it's the law
colors:
  primary:
    background: "#282828"
    foreground: "#ebdbb2"

Zsh with the good stuff:

# .zshrc essentials
plugins=(
  git
  zsh-autosuggestions
  zsh-syntax-highlighting
  docker
  kubectl
)

# Aliases that save my sanity
alias ls='exa --icons'
alias cat='bat'
alias vim='nvim'
alias gc='git commit -m'
alias gp='git push'
alias fucking='sudo' # sudo !!

The Neovim Rabbit Hole

My editor config is probably overengineered, but here are the plugins that actually matter:

-- Plugin manager: lazy.nvim (ironically not lazy)

-- Essential plugins:
- telescope.nvim  -- Fuzzy finder (cannot live without)
- nvim-tree       -- File explorer
- lualine         -- Status line
- mason.nvim      -- LSP installer
- nvim-cmp        -- Autocompletion
- treesitter      -- Syntax highlighting that doesn't suck

Window Management: Hyprland

Tiling window managers are peak productivity (after the learning curve):

# My keybinds (Mod = Super key)
Mod + Enter     = Launch terminal
Mod + D         = Launch rofi (app launcher)
Mod + H/J/K/L   = Move focus
Mod + 1-9       = Switch workspaces
Mod + Shift + Q = Kill window

It looks cool in screenshots and actually makes me faster once I stopped accidentally closing the wrong window.

Backup Strategy

Because I’ve learned this lesson the hard way:

# Dotfiles: Git repo
# System: Weekly snapshots with Timeshift
# Important stuff: Synced to cloud
# My dignity after breaking X11: Unrecoverable

The Reality Check

Is Arch Linux objectively better than Ubuntu or Fedora? Probably not.

Do I enjoy the control and learning experience? Absolutely.

Would I recommend it to everyone? Hell no. Use what works for you.

But do I use Arch BTW? You bet I do.

Resources That Saved Me

  • Arch Wiki - Literally everything you need
  • r/unixporn - For ricing inspiration
  • StackOverflow - For when things break
  • Twitter Linux community - Surprisingly helpful

That’s my setup. It’ll probably change next month when I discover some new tool and spend a weekend integrating it. But that’s half the fun, right?

If you’re thinking about trying Arch, go for it. Just maybe do it on a weekend when you don’t have important deadlines. And keep the wiki open.

- Dhanur