The Problem with Chat
The article argues that real-time chat interfaces create pressure for immediate responses, discouraging thoughtful, reflective communication. It contrasts chat with asynchronous formats like email and forums, which allow more time for careful consideration and editing before replying.
Background
- The essay contrasts three computer interfaces: **command line** (precise but hard to learn), **direct manipulation/GUI** (intuitive but inefficient for complex tasks), and the rising **chat interface** (e.g., ChatGPT, Slack, Discord).
- The author argues chat interfaces combine the worst of both worlds: conversations scroll away with no permanence, you can't precisely reference or manipulate individual items, and outputs can't be composed into other tools.
- Chat is a **sequence of messages**, not a **structured document** or a set of manipulable objects — making it ill-suited for iteration, revision, or asynchronous collaboration, which are central to knowledge work.
- The piece criticizes the tech industry's rush to chat-based UIs, suggesting it ignores decades of human-computer interaction (HCI) research on why different interface styles suit different tasks.