The Debug Adapter Protocol is a REPL protocol in disguise

A developer just turned a debugging pipe—officially the Debug Adapter Protocol (DAP)—into a talkative, type-and-get-results console (a REPL). DAP was built so editors can chat with debuggers, not to be your everyday command prompt, but thanks to its “evaluate” command and expandable data trees (think click-to-open folders of values), it works suspiciously well. There’s even a demo of drilling into structured results like a data detective. The crowd’s reaction? Equal parts delight and side-eye. Some folks love the clever repurposing, calling DAP a Swiss Army protocol that does more than it says on the tin, while others mutter, “Cool hack, but is this… a good idea?”

Then o11c dropped a spicy question: is the reported “type” the static one (what the code says) or the dynamic one (what it actually is at runtime)? Boom—instant type wars. Purists want crystal-clear semantics; pragmatists shrug and say, “Does it help me debug or not?” Meanwhile, jokers christened it REPL cosplay and rolled out the classic “Debugger? I hardly know her” meme. The strongest opinions split between: use the right tool versus use whatever works, with a chorus asking for clarity on types. If you like drama with your dev tools, this thread has everything—innovation, nitpicks, and nerdy punchlines. Check the protocol specs if you dare: DAP docs.