Comment by its-summertime
1 day ago
From the complete opposite side, I've built some tiny bits of near irrelevant code where python has been unacceptable, e.g. in shell startup / in bash's PROMPT_COMMAND, etc. It ends up having a very painfully obvious startup time, even if the code is nearing the equivalent of Hello World
time python -I -c 'print("Hello World")'
real 0m0.014s
time bash --noprofile -c 'echo "Hello World"'
real 0m0.001s
What exactly do you need 1ms instead of 14ms startup time in a shell startup? The difference is barely perceptible.
Most of the time starting up is time spent seartching the filesystem for thousands of packages.
> What exactly do you need 1ms instead of 14ms startup time in a shell startup?
I think as they said: when dynamically building a shell input prompt it starts to become very noticable if you have like 3 or more of these and you use the terminal a lot.
Ah, I only noticed the "shell startup" bit.
Yes, after 2-3 I agree you'd start to notice if you were really fast. I suppose at that point I'd just have Gemini rewrite the prompt-building commands in Rust (it's quite good at that) or merge all the prompt-building commands into a single one (to amortize the startup cost).
2 replies →