@0x4d6165 there is a case to be made for writing a first draft in ed (seriously!) I accidentally figured this out while using ed in part of a project of mine as an experiment.

Ed's insert mode is actually pretty ideal for getting into a flow state. You commit things one line at a time. The line can be as long as you want. (I think) you can use emacs/vi key bindings with rlwrap to edit the line. But once you hit enter, the line is in, and you're onto the next thought.

@jack @kkarhan @mwl Given the current zeitgeist someone, somewhere, RIGHT NOW, is working to embed Claude or Gemini in the ed(1) command prompt. And they're going to end up giving it a dependencies on Gtk and react.js.

https://mastodon.sdf.org/@jack/116190242608001379

For whomever needs to hear this: you are not alone. I am not vibecoding any of the software I write. I write it all by hand. I have leveled up to using ed(1) on a glass TTY rather than a hardcopy-output device. I am modernizing my stacks and using languages with excellent compilers like C89. I think about how to do more with less. I am trying to combine the best human-written libraries and modules and assemble them with minimal boilerplate. I enjoy reading manuals and references. I believe in robust, secure, human-written software.

@mntmn

@ed1conf I used to use EDITOR=ed on a Pinephone with swmo, so my messages were written in an ed(1) session inside a foot(1) pty.

However I read messages in my pager which was less(1).