Comment by arionmiles

You only notice this stuff if you use shell very often, and practically live in the command line. Since I started my career I've been using omz and a fresh install is always snappy but over time it starts getting slow.

Debugging/profiling why it's gotten slow has mostly been an uphill battle for me. I tried using zprof which pointed that compdef and compinit were culprits. I tried changing my config to calculate compinit only once a day since most people reported it to work, but it never worked. This kind of stuff pokes and stabs at you endlessly.

OMZ being shell, and being a maze of a codebase, I couldn't track down if and where compinit was being called from even after the config change above, because all profilers pointed to the possibility of compinit being called twice.

I gave up and started using barebones zsh + starship because I do need a good prompt. Yet the issues persisted.

I recently started using fish + starship on my local machine so that I could evaluate it before committing to it at work. It's the fastest shell so far (maybe because its new, I intend to find out).

My only painpoint now is I have a bunch of utility functions I've maintained in bash that I need to port to fish because of the posix incompatibility.

OMZ is absolutely bloat.