Proposes a radical redesign of terminal infrastructure by combining Jupyter-like notebook interfaces with shell integration, transactional semantics, and persistent sessions. The vision includes features like undo/redo for commands, dataflow tracking, sandboxed process execution, and structured terminal logs. The author outlines a four-stage incremental adoption strategy: starting with transactional CLI semantics, adding persistent sessions with client/server architecture, implementing structured RPC with metadata-tagged I/O, and finally building a Jupyter-like frontend. This approach aims to solve longstanding terminal limitations while maintaining backward compatibility and low switching costs.
Table of contents
a mental model of a terminalwhat does a better terminal look like?how does that work?ok but how do you build thisjyn, what the fuckbibliography3 Comments
Sort: