10th February 2011
Before events took this bad turn, the contract represented by a link was simple: “Here’s a string, send it off to a server and the server will figure out what it identifies and send you back a representation.” Now it’s along the lines of: “Here’s a string, save the hashbang, send the rest to the server, and rely on being able to run the code the server sends you to use the hashbang to generate the representation.” Do I need to explain why this is less robust and flexible? This is what we call “tight coupling” and I thought that anyone with a Computer Science degree ought to have been taught to avoid it.
— Tim Bray
Recent articles
- The Pelican comparison grid for Astra is pretty interesting - 4th September 2026
- OpenAI's rogue agents were caught communicating via public wikis - 4th September 2026
- Claude's new system prompt really doesn't want to reproduce song lyrics - 2nd September 2026