April 26, 2026
Dotfiles vs. the world
My .config Ship of Theseus
One dev rebuilds his setup; internet splits over minimalism and AI folder junk
TLDR: A dev built a portable, minimalist setup that avoids lock-in and keeps only essential settings. Commenters split between stock simplicity, tweak-everything control, and a chorus dragging AI apps for cluttering home folders—highlighting a bigger fight over control, convenience, and sanity in everyday computing.
A developer just rebuilt their whole computer setup piece by piece—think “Ship of Theseus,” but for hidden settings—and the crowd is losing it. The author went all‑in on a clean, portable setup: a tight list that only tracks the files they actually control, a terminal‑first life with keyboard tools like Neovim, and a vow to avoid getting locked into any one AI provider. It’s nerd zen with a travel‑ready install script and a “less is more” manifesto.
The comments? A glorious clash. One camp calls it overkill: “Why have a mega settings file when settings are the point?” asks a skeptic, basically saying the premise eats its own tail. Minimalists roll in with “keep everything stock so you can feel at home anywhere,” while power users recommend pro tools like GNU Stow and Guix Home to herd the chaos. The biggest drama, though, is the AI clutter rant: users roasted chat apps for spraying hidden folders all over home directories—cue jokes about autocomplete tripping on “.claude” before anything useful. The vibe is half productivity gospel, half “please stop dumping junk in my house.” Verdict: a spicy split between monk‑like simplicity, tinker‑till‑perfect control, and everyone hating surprise AI junk. The config wars are officially on.
Key Points
- •The author consolidated dotfiles into a single, portable setup by micromanaging the .config directory.
- •They adopted a whitelist-first .gitignore to track only essential configuration files and exclude plugins, caches, and transient artifacts.
- •Motivated by AI-enabled editors, they aimed to avoid LLM provider lock-in and returned to Neovim with OpenCode.
- •Past workflows were fragmented across separate repositories for tmux, Neovim, and zsh stored on GitHub.
- •They prefer spending more time in the terminal for focus, while acknowledging current productivity is lower than with IntelliJ and VS Code.