> A lot of steno's vaunted speed comes from very heavy use of macros. It's more than that: classic steno's not at all about saving operator time and labour or

> A lot of steno's vaunted speed comes from very heavy use of macros. It's more than that: classic steno's not at all about saving operator time and labour or generating a final text quickly, and in fact it sacrificed both of those goods in pursuit of its actual goal of being able to transcribe speech in real time. The operator bashes out a crabbed and idiosyncratic shorthand in real time, then he or she traditionally had to rework that into a fair copy later. Computerisation has apparently made steno with automatic, real-time reworking a reality, but if you want a system for people who do their own text input and want final results immediately (especially for text-based interaction like a command line) steno is still not the obvious place to start from. Velotype/Veyboard https://www.velotype.com/en/ https://www.velotype.com/en/ / http://www.veyboard.nl/en_main.html http://www.veyboard.nl/en_main.html https://en.wikipedia.org/wiki/Velotype https://en.wikipedia.org/wiki/Velotype seems like a better starting point: another fast two-handed chording system, but probably more "honest" and more suitable for interactive input.