I use Fish as a user shell everywhere I can and end up using Bash daily for scripting and on servers/VMs/containers at work, I've also been using Nushell a lot recently for personal scripts.
Biggest drawbacks for me is mixing up a few bits of syntax and some software doesn't ship Fish completion scripts, although I never write scripts in Fish which reduces the syntax I actually use.
In my opinion Fish is worth it just for the auto complete suggestions alone, but I also really like the way it handles editing config, it's sane default config, understandable error messages, and plug-ins.
Nushell is very nice, but I find it doesn't match the usability of Fish for interactive shells. Love it for scripts though.
That's correct in the most of the English speaking world, apple juice is what it sounds like, cider is fermented apple juice (as far as I'm aware, it is in the UK). In American English cider is apple juice, and hard cider is fermented, alcoholic apple juice.
Biggest drawbacks for me is mixing up a few bits of syntax and some software doesn't ship Fish completion scripts, although I never write scripts in Fish which reduces the syntax I actually use.
In my opinion Fish is worth it just for the auto complete suggestions alone, but I also really like the way it handles editing config, it's sane default config, understandable error messages, and plug-ins.
Nushell is very nice, but I find it doesn't match the usability of Fish for interactive shells. Love it for scripts though.