4 ms·
> [Sam] is one of the first editors to separate its UI from the actual editor - Sam can be used on both the command-line and as a graphical text editor. Not ev
by ScottBurson 9y ago
> [Sam] is one of the first editors to separate its UI from the actual editor - Sam can be used on both the command-line and as a graphical text editor.
Not even close to the first. TECO had both command-line and graphical editing in, ah, 1964: https://en.wikipedia.org/wiki/TECO_(text_editor)#History https://en.wikipedia.org/wiki/TECO_(text_editor)#History
- connorelsea 9y agoTIL about punch card hot code swapping
- fallat 9y ago> one of the first vs > the first But cool anyway. Maybe we should see how TECO manages its data too.
- kragen 9y agoThere were different implementations of TECO (written in the assembly languages of different machines) that had different user interfaces. That does not in any way imply that TECO had an editor process using a defined protocol to communicate with its UI process; in fact, in 1964, TECO ran on two computers, and neither of them had separate processes, or an operating system to run them under. ITS development hadn't started yet. As far as I know, all the implementations of TECO, even today, glom the screen update logic (if any!) together with the editor-buffer logic in a single monolithic process.
- WalterBright 9y agoIt is reputed that someone wrote a Fortran compiler in TECO on a dare.
- wglb 9y agoAh, TECO. I still have some muscle memory of TECO on the PDP-10. Line noise indeed.