←back to thread

457 points benoitg | 1 comments | | HN request time: 0s | source
Show context
b0a04gl ◴[] No.44365467[source]
every time your shell takes 100ms to render git status that you didn’t even need, you're paying invisible tax on flow. terminals should be reactive memory tools, not passive decoration. we optimize for code runtime but not for our own typing latency
replies(7): >>44365953 #>>44366256 #>>44366413 #>>44367231 #>>44367246 #>>44367362 #>>44367371 #
OptionX ◴[] No.44366413[source]
we optimize for code runtime but not for our own typing latency

100ms optimization is a lot different for a CPU or a human brain. I'm not defending having the entire system log dumped out on every prompt but a few amenities are worth a few milliseconds computation time for a human.

Besides, I don't see how, for example , having your prompt take those 100ms to print a git branch or status breaks your "flow" yet having to type out the commands yourself and taking longer doing it doesn't.

Its a balance between bloat and and usability like so many other things, but, to me at least, being on either extreme of bloat or extreme-minimalism seems counterproductive.

replies(1): >>44367950 #
1. naniwaduni ◴[] No.44367950[source]
100 ms is an incredibly long time even for humans.