> Developers do not work in teams for the work they do in terminals.
A lot of HNers might be lone wolves, but mentoring juniors and working with cross-functional team members definitely requires sharing terminal sessions.
> It does not disappear, for every common configuration I'm aware of. The history persists.
Commands history persists, within your machine, not necessarily across machines or environments usually (unless you’ve setup elaborate config for that).
But more importantly, I often find my self hoping that output history for each command could be saved too - so I know what happened, what went wrong/right last time, etc etc.
> This is completely irrelevant and misleading for something you actually do on one machine.
Again, it’s not easy to carry over configuration and tooling across machines. Very often, machines I ssh into are missing a lot of my custom config and it’s a pain to re-adapt in the thick of it.
> The most complicated thing I do with terminals is to type text.
IME it super painful to build a shell config that works across Mac/Win/Linux that reliably does word selection, jumping, home/end, etc. I sorely miss all these shortcuts that I easily get in my text editor or IDE.
> pressing tab already offers because of the descriptions
Exactly that though. Autocomplete hovering and providing context is way easier than typing part of the command and pressing tab again and again to see if the completer finds anything.