zsh-bench VS oh-my-fish

Someone's made a benchmarking system for zsh: https://github.com/romkatv/zsh-bench#premade-configs

Of course, their config is the best according to the benchmark (and ohmyzsh is the slowest option), but DIY configs are also covered, particularly possible performance optimizations.

Unfortunately, running exit is not a great strategy for running benchmarks. For zsh specifically, plugin managers are optimized for fast exit.

romkatv did a great write-up and benchmark within the context of zsh[0]. It's a great read.

[0] https://github.com/romkatv/zsh-bench#how-not-to-benchmark

Given the addition of async rendering in the latest release of spaceship, I wasn't sure whether I should include performance in the list of features found in powerlevel10kbut but not in spaceship. I used zsh-bench to benchmark powerlevel10k on my laptop running on battery (I'm writing this on a train) with a config that makes powerlevel10k looks similar to spaceship. I simply ran p10k configure and chose what looked most similar: Lean Style, UNICODE, 256 colors, two lines, etc. Here are the benchmark results:

Obligatory link since you are engaging in profiling interactive zsh: https://github.com/romkatv/zsh-bench.

1.) It's fast. Like, really fast. 1.) It supports deferred loading via zsh-defer 1.) It supports local plugins as well as ones hosted via a git provider (aka: GitHub, GitLab, BitBucket, etc) 1.) The codebase is simple and easy to understand and contribute to 1.) It supports git branches (with tag/shas on the roadmap) 1.) It supports partial plugin loading such as loading Oh-My-Zsh plugins and Prezto modules without loading the whole framework. 1.) There's an easy migration path from legacy plugin managers like Antigen/Antibody. 1.) Plugins are managed via a simple plugins file that makes it easy to share your config with others. 1.) And lots more

In any case, slow zsh startup is always caused by whatever you put in zsh startup files and it's always possible to reduce zsh startup to imperceptible levels without sacrificing any functionality by editing said startup files. There is a bit of info on interactive zsh performance at https://github.com/romkatv/zsh-bench.

Why is this a good thing? Is this a proxy for performance? If so, you can measure performance directly with zsh-bench. This way you can describe the advantage in terms that have real value to end users. For example, you can say that the first prompt appears N milliseconds faster when using Zpy than if you were using something-else.

[1] https://github.com/oh-my-fish/oh-my-fish

Despite these attractive attributes, many developers I've come across don't prefer Fish shell, primarily due to integration gaps with tools like Python's virtualenv. So, in this article, I'm offering a simple solution for automatic virtualenv activation for Fish shell, steering clear of resource-intensive frameworks like oh-my-fish that often slow down the shell.

I use Alacritty with Oh My Fish!

I use fishshell, and its Oh my fish framework as my command line shell. Over the years, I have gathered many useful functions and shortcuts. Here are my favorites.

13.) Install oh-my-fish - link ~> https://github.com/oh-my-fish/oh-my-fish $ git clone https://github.com/oh-my-fish/oh-my-fish $ cd oh-my-fish $ bin/install --offline

Moreover, there are tools were made on top of those to provide more functionalities, and fill some of the gaps, for instance, oh-my-zsh, Prezto, oh-my-fish, and much more. However, the default embedded terminal in macOS is still lacking something. That's why iTerm and other terminal like Hyper. It provides you a set of customization to boost your productivity.

Frankly, omf is not in a good place, maintenance-wise, and that has been brought to the maintainer's attention - https://github.com/oh-my-fish/oh-my-fish/issues/788.

Windows Terminal + wsl2 sa fish i oh my fish je super ako zelis nesto sto radi dobro i ugodno je oku out of the box