The concept of a plugin has evolved dramatically in modern software architecture, especially with the rise of intelligent agents. But what exactly is a plugin today, and how does it fit into this new landscape? There is a certain kind of conversation that happens late in the afternoon, usually between someone who builds things and someone who helps them think, in which the original question evaporates entirely and something more interesting takes its place. You start by asking about plugins. You end up redesigning how software should work for the next decade. Nobody planned it that way. These are the best conversations.
What exactly is a plugin, anyway?
For most of the history of software, the answer was obvious. A plugin was a thing you bolted onto an existing system to extend it. You had your browser, and then you had Flash. You had Photoshop, and then you had filters. You had WordPress, and then you had approximately forty thousand plugins, roughly thirty-nine thousand of which were security vulnerabilities wrapped in good intentions. A plugin was the trapdoor built into software by people who knew they couldn’t anticipate everything, a small architectural confession that said: we couldn’t finish this, but maybe someone else can.
…
Read the full article on Nspirement
Comments