From 98142bb495896c4084b2511f1f031e799c7f4b0e Mon Sep 17 00:00:00 2001 From: Craig Jennings Date: Sat, 18 Jul 2026 20:03:16 -0500 Subject: docs: document single Dupre theme Remove retired theme-switching guidance and Hudson references from active documentation. --- docs/2026-06-10-tool-evaluation-criteria.org | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'docs/2026-06-10-tool-evaluation-criteria.org') diff --git a/docs/2026-06-10-tool-evaluation-criteria.org b/docs/2026-06-10-tool-evaluation-criteria.org index f5fec34..be0a79a 100644 --- a/docs/2026-06-10-tool-evaluation-criteria.org +++ b/docs/2026-06-10-tool-evaluation-criteria.org @@ -14,7 +14,7 @@ A replacement tool earns adoption only when it beats the incumbent on a dimensio * Weighting criteria (compare on these) - Daily-use win: does it remove a real friction, or is it novelty? "Answers in one command what took a pipeline" (dust) beats "same answer, prettier" (gping). - Workflow fit: Emacs (dired, vterm, magit) and tmux already own many niches. A candidate duplicating them adds maintenance surface without adding capability (see: terminal tabs/splits, broot vs dired+zoxide). -- Theme-system fit: can set-theme drive it (INI/TOML include, runtime color escape, reload signal)? Tools that can't follow dupre/hudson stay second-class. +- Theme-system fit: can the Dupre apply path drive it (INI/TOML include, runtime color escape, reload signal)? Tools that cannot follow the desktop palette stay second-class. - Packaging: official repo > AUR > git build. Every step down adds update fragility to fresh installs. - Migration cost: config translation, muscle-memory retraining, installer changes. Cost scales with how load-bearing the incumbent is. -- cgit v1.2.3