sl0ppty: a README for people, not for the person who wrote it

The old one was an essay. It explained the reasoning behind the split guide,
the budgeting rule shared by the tab strip and the status line, and the exact
mechanism by which images are re-emitted -- all true, all in DESIGN.md, and
none of it what somebody deciding whether to run this wants to read.

Rewritten as: what it is, why it exists, how to install it, the keys, what
the mouse does, what makes it different, how to configure it, how to script
it. Half the length, no design commentary, links out for the rest.

The "why" was also wrong. It said this exists because agent sessions want
programmable chrome. That is a thing it does, not the reason it was written.
The reason is that the existing multiplexers are crusty in ways that follow
from their architecture -- stored layout state, mouse handling that
duplicates the drawing, extension models bolted onto a core that never
expected one -- and a fork carrying sixty-odd patches was spending its effort
arguing with that rather than multiplexing. Hence starting over, on top of
Mitchell Hashimoto's terminal core rather than pretending that part is easy.

0 files changed, 0 insertions, 0 deletions