Good software knows when to stop

Original Article ↗ Hacker News Discussion ↗

Modern software is often criticized for endless feature creep, enshittification, and AI hype, driven more by growth and VC incentives than by user needs or product fit. Commenters contrast “finished” or narrowly focused tools — from core Unix utilities to editors like Vim and Sublime Text and messengers like Signal — with products like Evernote, Dropbox, Spotify, and big games that became bloated or alienated their users by chasing new features. Many argue that the hardest and rarest discipline in software is knowing when a product is good enough, declaring it feature-complete, and limiting changes to maintenance, performance, and security.

AI Branding and “AI Everywhere”

  • Renaming products to include “AI” (e.g., databases) is seen as hype-driven; some expect names to revert once AI becomes mundane infrastructure.
  • Others argue this doesn’t match what users actually need from those tools, and see it as marketing and careerism, not product fit.
  • Some fear OS-level AI integration enough that they’d switch distros; others are pessimistic there will be “clean” alternatives.

Feature Creep vs “Finished” Software

  • Strong support for the idea that good software has a clear purpose, narrow scope, and eventually stops adding features.
  • Examples praised: ls, coreutils (with a high bar for new flags), Sublime Text, vim/vi, simple note or uninstall tools, Signal.
  • Counterpoint: even “simple” tools like ls have large option sets; a linked analysis of CLI complexity is referenced.
  • Many complain about enshitification: Dropbox, Evernote, Spotify, modern Windows/Office/Teams, Notepad, and note apps like Obsidian drifting from lean, focused designs.

User Requests, Nostalgia, and Product Direction

  • Extensive debate around games like World of Warcraft, Old School RuneScape, Ultima Online, Diablo II as analogies.
  • One camp: users clearly knew they wanted “classic” versions; ignoring them was costly.
  • Another camp: the deeper need was a certain design ethos; “classic” was a proxy for “stop bolting on systems that ruin the feel.”
  • Broader takeaway: “ignore feature requests” is too simplistic; understanding underlying problems is hard and requires humility.

Business Models and Incentives

  • VC and subscription/SaaS models are blamed for pushing endless features, pivots, and revenue extraction over product quality.
  • Boxed software and one-time licenses are remembered as more compatible with “finished” products, though they had upgrade and compatibility issues.
  • Some accept subscriptions as rational for tools that must track new hardware/formats; others see them as primarily about shareholder value.

Maintenance, Stability, and Trust

  • Users struggle to tell “feature complete and stable” from “abandoned,” especially on platforms like macOS/iOS that deprecate APIs quickly.
  • Fear: adopting a tool that later breaks or is shut down (SaaS) versus missing bug/security fixes in unmaintained code.
  • Compliance and security expectations push teams away from libraries that appear dormant.

Unix Philosophy and Minimal Tools

  • Several comments frame the article as rediscovering the Unix philosophy: small tools, clear roles, composability.
  • Others note a contrary trend toward giant, vertically integrated systems and AI agents that try to “do everything,” often inefficiently.