←back to thread

457 points benoitg | 1 comments | | HN request time: 0.204s | 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 #
Twirrim ◴[] No.44365953[source]
Starship is very fast, taking only a couple of milliseconds to gather the data (and you can easily configure it to minimise what it'll spend time gathering). It's night and day compared to other ones I've tried, where the hundred millisecond-ish delays annoyed me.
replies(2): >>44366322 #>>44372064 #
Night_Thastus ◴[] No.44366322[source]
Depends a lot on the system. I tried using it on Windows via MSYS2, and it seems like some Windows overhead (maybe process startup?) was causing Starship to slow it all down to a crawl. Disabling a few of the addons helped but didn't fix it. In the end I stopped using it.
replies(2): >>44366809 #>>44370818 #
1. pxc ◴[] No.44370818[source]
Windows' filesystem performance for tools that expect Unix is abysmal, and it gets drastically worse in most corporate environments because endpoint security software hooks into the filesystem drivers to instrument all file access.

Git-aware prompts can't be recommended on Windows, imo.