But the whole reason I use fish is because I DON'T have to look things up on the internet because it uses sane syntax instead of some arcane combination of brackets, symbols, and the word “if” spelled backwards.

fwiw, we are shipping a number of features in fish 3.0 (any day now!) that are specifically targeting at maximizing compatibility with most bash scripts (still not POSIX).

That includes support for && and || and a few other things that should go a long way towards making most code you find drop-in ready.

I like using a different plugin manager with OMZ. https://github.com/tarjoilija/zgen

If you use a lot of addons, this can load up prompts faster without losing any OMZ goodness.

A quick tip for anyone disparaging the compatibility of fish shell, since this has solved most of the interior concerns for me:

  # Bash:
  FOO=bar ./command
  # Equivalent in bash and fish:
  env FOO=bar ./command

have you tried https://github.com/oh-my-fish/oh-my-fish ? has been serving me well for years

I'm in the same boat as you. Also used Fish for several years and loved it, but there's some incompatibilities here and there (dont remember exactly what, I think it was difference in how to pipe streams vs bash/zsh). In the end i switched to zsh & oh-my-zsh and haven't run into issues since (made the switch maybe 6 years ago). I'm a heavy terminal user so this part I'm not experimenting with again.

Same except using zplug.

I still use fish for scripting as its syntax is far more casual looking.