Not really. The emerged from different spaces. But both rely heavily on line-level editing, each for their own reason. For ed I can really recommend a great video by Kay Lack [1]. For Basic playing around with the Sunflower interpreter [2] and for context this paper by Annette Vee [3] on Dartmouth Basic.
Both, ed and Basic, had to deal with constraints in terms of how much could be shown on screen or printed. So 'screen estate' was limited and one way to deal with that is to focus on just on single lines. In both you hardly ever see the whole code file at once (let alone be able to mavigate around the file quickly on a visual level), but it still resides in memory. You just ask the program to show you certain lines. In ed with `2,4p` or `2,4n` to print lines 2-4 without and with line numbers. In Basic with `LIST 20 30` to show lines 20 and 30. The same for editing. You simply let ed or Basic know which lines to overwrite or edit, without moving there by mouse or keyboard visually.
Kay Lack's video made me realise to what extreme these constraints went, when you have no screen but just a printer.
[1] https://www.0de5.net/stimuli/the-little-editor-that-could
[2] https://hundredrabbits.itch.io/sunflower-basic
[3] https://www.digitalhumanities.org/dhq/vol/17/2/000696/000696.html
@mistergenest
#ComputerArchaeology #Editor #Lore