Linux Desktop AI Power User
Neuf outils open-source pour le dev Linux qui veut un desktop tilé, terminal-first et boosté IA : compositeur Hyprland ou Sway, bspwm en repli, tmux + Zellij, Neovim + LazyVim, Ollama en local et systemd pour la glu.
What's in this pack
This is the rig a working Linux developer would build on a fresh Ubuntu, Arch, Fedora, or NixOS install in a weekend — not a 50-package shopping list. Every pick here is open-source, actively maintained, and earns its tile of screen real estate. The order matters: each tool unlocks the next.
Unlike a Mac rig, Linux gives you actual choices at every layer — and that's both the point and the trap. This pack picks defaults that work across the four big distros, calls out where Wayland and X11 diverge, and tells you which choices are reversible versus which lock you in.
If you've already run Mac Weekend Essentials, this is the direct counterpart: launcher + tiling + terminal + editor + local AI, opinion-first, weekend-shaped.
Install in this order (WM → terminal → editor → local model → automation)
- Hyprland — dynamic tiling Wayland compositor. Start here if you're on Arch, Fedora 40+, or NixOS unstable. Animations, blur, rounded corners — surprisingly snappy for what it does. Default for any new install in 2026 unless you have specific reasons not to.
- Sway — i3-compatible tiling for Wayland. Pick this over Hyprland if you want stability over polish, already know
i3config, or run a multi-monitor laptop+dock setup where Hyprland still has rough edges. - bspwm — X11 tiling based on binary space partitioning. Your fallback when Wayland breaks (NVIDIA + external monitor, screen recording into OBS the old way, anything proprietary). Tiny binary, scriptable via
bspc, pairs withsxhkdfor keybinds. - tmux — terminal multiplexer. Even if you live in a tiling WM, you still want sessions that survive disconnect. tmux is the boring, universal, every-server-already-has-it choice. Detach with
prefix d, reattach from anywhere. - Zellij — modern alternative to tmux. Discoverable keybinds shown at the bottom of the screen, layouts as KDL files, plugin system in WASM. Use Zellij locally for the UX, keep tmux for remote sessions.
- Neovim — the editor. Lua-scriptable, async, LSP-native, Tree-sitter-driven highlighting. Don't write your own config from scratch in 2026.
- LazyVim — pre-configured Neovim distribution. Sensible defaults, lazy plugin loading, LSP + completion + Telescope wired up. Spend 2 hours customizing, save 2 hours/week forever. Kickstart.nvim is the alternative if you want to read every line yourself.
- Ollama — local LLM runner. One command (
ollama run llama3.1) and you have a local model answering questions in your terminal. Pair with Continue.dev orgen.nvimto get inline AI inside Neovim with zero cloud calls. - systemd — the init system on every modern Linux. Use user units (
~/.config/systemd/user/) to auto-start tmux sessions on login, restart Ollama when it crashes, schedule daily backups via timers. The glue layer that makes the other eight feel like one system instead of nine apps.
How they fit together (ASCII)
Display Server
├─ Wayland: Hyprland (default) or Sway (i3-style)
└─ X11: bspwm + sxhkd (fallback for NVIDIA / OBS / legacy)
│
▼
Terminal (alacritty, kitty, foot — pick any)
│
▼
Multiplexer
├─ Zellij (local, discoverable)
└─ tmux (remote, universal)
│
▼
Editor: Neovim under LazyVim
│
├──► LSP / Tree-sitter / completion
└──► Continue.dev or gen.nvim ──► Ollama (local LLM)
│
▼
GPU (CUDA / ROCm / CPU)
systemd user units glue everything: auto-start Ollama,
resurrect tmux, schedule timers, watch for config changes.
The WM + multiplexer + Neovim + Ollama core is the rig. Everything else is taste. Don't skip systemd user units — they are what turns this from a pile of dotfiles into something that survives a reboot without you babysitting it.
Tradeoffs you'll hit (Wayland vs X11, tiling vs floating)
- Wayland vs X11 — Wayland is the future, X11 is what works today with proprietary NVIDIA drivers, OBS Studio (pre-PipeWire workflows), Synergy/Barrier, and most screen-share apps. AMD/Intel GPUs: go Wayland. NVIDIA: try Wayland, expect to fall back to X11 once. Hyprland and Sway require Wayland; bspwm requires X11. That's why this pack ships both.
- Hyprland vs Sway — Hyprland is feature-rich and visually impressive; Sway is conservative and rock-solid. Pick Hyprland for solo dev workstation, Sway for the laptop you take to client meetings. They are not config-compatible.
- tmux vs Zellij — tmux is everywhere; Zellij is nicer. The grown-up answer is both: Zellij locally because the floating help bar saves you from memorizing 40 prefix keys, tmux on every server because it's already installed. Don't try to unify.
- LazyVim vs kickstart.nvim vs roll-your-own — LazyVim is opinionated and works on day one. Kickstart is a single ~600-line
init.luayou copy and own. Rolling your own is a yak shave that takes a year. Most senior Neovim users land on LazyVim and never look back. - Ollama vs llama.cpp directly — Ollama wraps llama.cpp with a model registry and a daemon. Use Ollama unless you specifically need llama.cpp's full flag surface for benchmarking.
Common pitfalls (NVIDIA-Wayland, audio stack confusion)
- NVIDIA + Wayland — works in 2026 with the open
nvidia-opendriver 555+, but Electron apps still flicker, Discord screen share is iffy, and some games refuse to launch. Test before you commit. Keep a bspwm + X11 session installed as your escape hatch. - PipeWire vs PulseAudio vs ALSA confusion — modern distros ship PipeWire with
pipewire-pulseshim. If audio breaks, runsystemctl --user status pipewire pipewire-pulse wireplumberfirst — all three should be active. Don't installpulseaudioon top of PipeWire; that's how you brick sound. - Hyprland config in
~/.dotfilessymlinked elsewhere — Hyprland reloadshyprland.confon change. If your symlink target moves, the watcher silently dies. Edit in place or usehyprctl reloadafter sync. - Ollama eating 16 GB of disk per model — models default to
~/.ollama/models. On a 256 GB SSD this fills up fast. Symlink to a larger disk early, or setOLLAMA_MODELS=/mnt/big/ollamain the systemd user unit. - tmux + true color — set
terminal-overrides ',xterm-256color:Tc'in~/.tmux.confor your Neovim themes will look washed out. - systemd user units not starting at login — you need
loginctl enable-linger $USERon headless boxes; otherwise units stop when you log out.
9 ressources prêtes à installer
Questions fréquentes
Ubuntu, Arch, Fedora, or NixOS — which distro pairs best with this pack?
All nine picks run on all four distros — that's why they made the list. Practical guidance: Arch gives you the newest Hyprland and the fewest packaging fights (use Yay for the AUR). Fedora 40+ ships Hyprland in the official repos and has the most polished Wayland experience out of the box. Ubuntu 24.04+ works but you'll add a PPA or build Hyprland yourself. NixOS makes the whole stack reproducible in one flake — best for the developer who wants this rig on three machines in sync. None of them are wrong.
Do I really need both tmux and Zellij?
Most senior Linux users run both for different reasons. Zellij locally because the help bar at the bottom of the screen means you never forget a keybind, layouts are KDL files you commit to git, and the WASM plugin system is fun to extend. tmux on every server because it's already installed everywhere, the muscle memory is universal, and the protocol is rock-solid over flaky SSH. Don't try to unify on one — they win in different contexts.
Can I run Ollama on a laptop without a discrete GPU?
Yes. Ollama auto-detects CPU-only mode and runs smaller models (Llama 3.2 3B, Phi-3, Qwen 2.5 7B quantized) at usable speeds on modern Intel/AMD laptops with 16 GB RAM. You won't get Claude-class quality, but for code completion, commit message drafting, and rubber-duck conversations it's fine. The big win is privacy — none of it leaves your machine. Add an external GPU (eGPU enclosure or a small workstation) later if you want to run 70B-class models.
Hyprland looks beautiful but I've heard it's unstable — true?
Less true in 2026 than it was a year ago. Hyprland 0.40+ is stable enough for daily driving if you stick to released versions and avoid the unstable plugin ecosystem. The remaining sharp edges are mostly NVIDIA-specific (screen tearing on proprietary drivers, occasional crashes when unplugging external monitors). If your laptop is AMD or Intel, Hyprland is fine. If it's NVIDIA, install Sway as a fallback session and don't lose sleep when one of them hiccups.
What about a launcher like Rofi or wofi — why isn't one in this pack?
Because Hyprland, Sway, and bspwm each ship documented integration paths for rofi (X11), wofi (Wayland), fuzzel (Wayland), or tofi (Wayland) and the right pick depends on which compositor you ended up with. Install whichever your WM's docs recommend first, then iterate. This pack focuses on the load-bearing pieces; launcher choice is a 10-minute decision after everything else is running.
12 packs · 80+ ressources sélectionnées
Découvrez tous les packs curatés sur la page d'accueil
Retour à tous les packs