> It seems like copy&paste are a challenging computer science problem [irony] You have no idea. Issues that cross my mind: - plain vs rich vs embedded: which

> It seems like copy&paste are a challenging computer science problem [irony] You have no idea. Issues that cross my mind: - plain vs rich vs embedded: which one to paste, and at that time, if applicable, how to degrade one into the other? ask the original app, which knows the semantic? store multiple versions? store once, as-is, and hope the target app knows how to handle it, leading to inconsistencies? - persistence across app life cycle: copy, close app, paste into other app. For years Linux, X or something simply could not do that and your paste would fail. - UI concerns: it's easy to take the current, refined by the years way to handle clipboard for granted. remember how at some point some implementations required you to click a button on a damn toolbar. Notice how competing alternatives exist, such as X autofill with selection buffer pasted with middle click, xterm's left click to move left + right click to move right, OSX's growth of selection to the closest selection edge, or the infamous quick mode CMD.EXE way that gets copied with enter. - security concerns: apps could be running with different levels of privilege, and you certainly don't want less privileged ones to have uncontrolled access to the clipboard buffer data, whose data may come from a more privileged source.