Unix shell - We can do better now
summary
Claim: the Unix shell still uses a 1974–75 telegraph paradigm and must evolve to interactive objects on the screen that plugins manipulate. Implementation: parse program output into structured data (jc/jq style), record interactions as semantic records (e.g., “instance launched by pipeline X” not ID 123), and expose plugin commands per object type. Built: an NGS language is already used at work; a JavaScript web frontend is under development and a terminal frontend is planned. Goal: reproducible replay and one‑click cloud navigation between CI, ECS logs, etc.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 0:27Rethinking interactive shells
- 1:30Shell communication history
- 2:571974–75 computing turning point
- 3:38Shell interactivity lag
- 4:41Semantic shell recording
- 5:43Parsing program outputs
- 7:05Modern shell UI objects
- 7:50Next-gen shell vision
- 8:32Next Generation Shell project
- 9:13CLI meets web ease
- 9:57Shell architecture overview
- 10:39Q&A
related talks
39mLinux Shell Debates or: How I Stopped Worrying and Learned to Love PowerShell
19mIt's a UNIX system, I know this!
48mThe Unix Way Seen by a DevOps
39mLeveling up in DevOps: the Art of Bad Shell Scripts
40mBash: the #1 Skill of a DevOps Engineer
49mState of The Shell
38mDesigning a Multi-Language Live Programming Tool With Phoenix and Genstage
38mTake Control. Write a Plugin. Part II