-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
-
ble.sh
Bash Line Editor―a line editor written in pure Bash with syntax highlighting, auto suggestions, vim modes, etc. for Bash interactive sessions.
-
tinytestlib
An MVP shell script testing library (currently bash but may include more shells in future) allowing you to assert on stdout, stderr and return codes in your shell script test suites.
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
In what ways is fish faster than zsh?
I can be believe it’s faster than a poorly configured zsh (which unfortunately is quite common), but would be curious to see actual test results, with things like “input lag”, “time to first prompt”, “command lag”, etc. like is measured with the excellent zsh-bench (https://github.com/romkatv/zsh-bench#what-it-measures)
What about Oh My Fish https://github.com/oh-my-fish/oh-my-fish
I've been using Fish for years and spend my entire day working with Python. Python's virtualenv has an `activate.fish` command, I've never had any problems with it. Additionally, we have a ton of internal tooling built in a fabfile, so I've written a couple of snippets of fish that automatically activate that .venv (Poetry managed) whenever I cd into a directory that has one, and also expands a bunch of env vars into the shell session. I've also got this feature request in on the virtualenv repo in the hope that one day we can have activate.fish emit an event - https://github.com/pypa/virtualenv/issues/1456
I used OhMyZsh for years with the Agnoster power line theme and over the years it got slower and slower. Tried Fish about 6 years ago and immediately spent the rest of the day tweaking an Agnoster theme to my liking because everything about it was better than Zsh and waaaay faster. My fork is here [0] for anyone interested, though the readme and screenshots are from the original.
[0] https://github.com/drcongo/agnoster
I love using oh-my-fish but I honestly thing a lot of people have moved to using fisher. Because of OMF's lack of updates.
https://github.com/jorgebucaran/fisher
Curious what issue you're seeing with mc? There was an mc fix in fish 3.2.1 [1] but we know of at least one remaining issue [2].
1: https://github.com/fish-shell/fish-shell/issues/7769
2: https://github.com/fish-shell/fish-shell/issues/6767
I stay with bash due to its 100% availability on all systems I use, with https://github.com/akinomyoga/ble.sh I got all the auto-complete I need too.
I tried bash first, with every bell and whistle added. I tried all the scripts and tuned my .bashrc and .bash_profile and PS1 and all the crap. It was a huge chore.
Then I tried switching to zsh with oh-my-zsh and all that. 42 million tunable bits and I still didn't get it to my liking.
Then I found Fish and 95% of the stuff was good enough out of the box. The only things I've really added was Starship[0] as a prompt - again good enough with pretty much zero configuration and fzf[1] for history search.
Now I use it everywhere, synced via Homeshick[2]
[0] https://starship.rs
I made the mistake last year of falling in love with xs-shell, talking to its maintainer (who recently put xs out to pasture, as it were) who is now moving all his stuff to es-shell, switching my romance to es-shell, merging in 2 forks of it to my own version https://github.com/pmarreck/es-shell/ aaaand having a kid and basically running out of time.
This shell makes a ton more sense to my brain than the usual bash/zsh/fish rigmarole, it just needs some love.
The last thing I was working on was a way to capture all of stdout, stderr and return code from a single run of a command, for testing purposes, because the OTHER thing es-shell desperately needs is a proper test suite. I figured one out for bash https://github.com/pmarreck/tinytestlib but not one for es yet.
I made the mistake last year of falling in love with xs-shell, talking to its maintainer (who recently put xs out to pasture, as it were) who is now moving all his stuff to es-shell, switching my romance to es-shell, merging in 2 forks of it to my own version https://github.com/pmarreck/es-shell/ aaaand having a kid and basically running out of time.
This shell makes a ton more sense to my brain than the usual bash/zsh/fish rigmarole, it just needs some love.
The last thing I was working on was a way to capture all of stdout, stderr and return code from a single run of a command, for testing purposes, because the OTHER thing es-shell desperately needs is a proper test suite. I figured one out for bash https://github.com/pmarreck/tinytestlib but not one for es yet.
I've been using fish for 2 years now and I pretty much live in the terminal. I would feel handicapped without it.
Just use fish and use shebangs `#!/bin/sh` (which should be in your scripts anyways) and you can keep writing/running POSIX scripts all day. I think it's the best option until nushell[0] is ready.
As an added bonus now that you don't use bash interactively you can substitute dash[1] and increase the speed of most POSIX scripts, win-win.
I'd also recommend zoxide[2], i feel like it's one more must have no matter what you do in the shell.
[0]: https://github.com/nushell/nushell