Post B5CN7BCXHPTCOikWVk by jlundell@ioc.exchange
 (DIR) More posts by jlundell@ioc.exchange
 (DIR) Post #B5CCiEcqPbwGEkWPQm by tomjennings@tldr.nettime.org
       2026-04-11T20:52:29Z
       
       0 likes, 0 repeats
       
       So histories on the metaphors used in computer editing of text have been done, no surprise.  Only skimmed these myself, will read later. In the timeline I'm in, there were coding sheets (recognizable; but never used though I did some hand coding), then the paper tape editors themselves (teletype reader, punch, edit one line at a time), then the "ed" family (that incorported the P.T. editors but had the crazy idea of a "screen"; includes ed, teco, emacs), then the widespread deployment of meece when it all ends and turns to shit with far too many options and our documents all looking the same "professional" (sic). Pretty page,  totally misses all points:https://www.linkedin.com/pulse/evolution-text-editors-word-processors-miguel-rivas-perez-ilwbcOh, this one has much clue. And one of the few writings that makes it clear that the creation of jaquard loom cards was solidly "programming", in that it required fairly arbitrary transformations of data. It would not surprise me to find a loom that could count, and stop or something. Also: "women's work", an important story itself in computing generally.https://lug.ncsu.edu/presentations/2019-11-13-text-editor-history.pdfThis idiosyncratic wiki isn't analysis or anything, but a good survey, emphasis in the early micro era. But digging out anything from the 50s and 60s would be serious work. Clearly a work of love here.https://texteditors.org/cgi-bin/wiki.pl?HomePage
       
 (DIR) Post #B5CKfGdpGBh7Fm4orY by jlundell@ioc.exchange
       2026-04-11T22:21:35Z
       
       0 likes, 0 repeats
       
       @tomjennings In the 70s, I helped write and then maintained a full-screen editor with a data-entry mode modeled on an 026 with program cards.The editor’s source itself existed in the form of four boxes of punched cards–I’d estimate 7000+ cards in all. I can’t remember if I ever moved the master source to disk. Raytheon 70x assembler.
       
 (DIR) Post #B5CMQSfgRznQ810tfc by tomjennings@tldr.nettime.org
       2026-04-11T22:41:20Z
       
       0 likes, 0 repeats
       
       @jlundell Wow.
       
 (DIR) Post #B5CN7BCXHPTCOikWVk by jlundell@ioc.exchange
       2026-04-11T22:49:02Z
       
       0 likes, 0 repeats
       
       @tomjennings just thinking about makes me want to take a nap
       
 (DIR) Post #B5CNc3E8ye1OdyDpkO by tomjennings@tldr.nettime.org
       2026-04-11T22:54:39Z
       
       0 likes, 0 repeats
       
       @jlundell I never worked with cards, not even once. The physicality is cool, if daunting, the gear seems monstrous.
       
 (DIR) Post #B5CxxFoswxWC87ojxY by gunstick@mastodon.opencloud.lu
       2026-04-12T05:41:48Z
       
       0 likes, 0 repeats
       
       @tomjennings I started using vi about 35 years ago. I still use vi today.
       
 (DIR) Post #B5DJcBXjqwcrmE9itc by dec23k@mastodon.ie
       2026-04-12T09:44:32Z
       
       0 likes, 0 repeats
       
       @tomjennings That's a great wiki.I used a bunch of them early on, but I settled on CygnusEd (Amiga) and QEdit (PC) for regular use.Then tried a few of the most common *nix editors (including emacs and vi, while aware of the holy wars), and settled on Vim.
       
 (DIR) Post #B5DoZVK4xAEEpgy5fU by tomjennings@tldr.nettime.org
       2026-04-12T15:31:26Z
       
       0 likes, 0 repeats
       
       @dec23k Its a great wiki isnt it!I remember many names but have tried very few. I am now checking some out out of "academic" interest, but actively looking for a good one for mp/m, which has troubles with cp/m programs that cheated; most of them, due to CPMs shit console api. Wow there's some terrible programs oit there. But a handful of very good programs. Im curious too about the "notable programmers" choices; ima gonna check those out, when persistent people use something a long time it means theyve found s path through it that's functional, though thst path may not be one i will over use...!