reply
> By the way, 'em' stands for 'editor for mortals' - I christened it that after Ken Thompson visited our lab at QMC while I was developing it and said something like: "yeah, I've seen editors like that, but I don't feel a need for them, I don't want to see the state of the file when I'm editing".
replyLiterally an insane opinion.
To be fair, I sometimes edit files with ed. Especially the ones I've seen hundreds of times (eg /etc/ssh/sshd_config).
replyNowadays we're dealing with orders of magnitude more code. Back in the day it would've been fine for the programs you wrote yourself.
>Back in the day it would've been fine for the programs you wrote yourself.
replyI mean, maybe if your code was simple enough that you could keep the entire state in your head at once, but we're talking about guys writing memory management routines and OS kernels. In C. With no LSP, no syntax highlighting, no linting, etc.
It's one thing to say "my hardware is too limited, I can't fit all that extra context into memory", but to be working with that tech stack and to say "I actively choose not to see the context around the line of code I am editing at this instant in time" is just obtuse, no matter how many programming languages you've invented.