4 ms·

Any thoughts on fish as compared to nushell [0]? It's similar to PowerShell in its philosophy and is also written in Rust. [0] https://github.com/nushell/nushe

Any thoughts on fish as compared to nushell [0]? It's similar to PowerShell in its philosophy and is also written in Rust. [0] https://github.com/nushell/nushell https://github.com/nushell/nushell

yencabulator 3y ago
Here's my experience of spending a part of a day with each: Fish: - customizing or debugging Fish's completion was utter torture; the defaults are horrible like "carTAB" completes to "blkdiscard" when I don't have cargo in PATH - nothing in Fish seems to have a useful `--help`, no useful summaries & quick refreshers, just punt the user to a big verbose man page Nushell: - no job control, no background jobs - error handling is utterly broken - control-C breaks unexpected things, what gets aborted seems up to luck (e.g. aborts the prompt building) - globs inside quotes, `ls "*"` - lots of weird parsing errors & bad edge case behavior
- hammyhavoc 3y ago
  What's your preferred daily driver instead?
  - yencabulator 3y ago
    I'm still on bash. I was really hopeful on nushell until I discovered the error handling & control-C -- before those I thought it was "just" lack of job control, now I'm less enthusiastic about the quality.
    - hammyhavoc 3y ago
      Looks like I'll be staying on Bash! It somewhat amuses me that we don't seem to have done better than it in all these years—but I also take a lot of comfort in that. With that said, it still gets updates! So, it can and is still improved. :- ) Hard to compete with such a mature offering.
TheFuzzball 3y ago
I've used Fish for a while (my dotfiles tell me I've been using it for 8 years now... how the time flies! [0]) and decided to give Nu a try. The main problem with Nu is that it can't really be used as a full-time shell because it doesn't support job control, so a lot of nodejs-based CLIs I need for my job seem to lock up the shell. I got around it by using pueue (a daemon that manages processes), but it's clunky to say the least. I do think it'll get better as it matures, but I've been through all that pain with Fish and I'm not sure I want to put myself through that again. [0]: https://github.com/LukeChannings/dotfiles/blob/148a5021da464ec886aff077c6ea1bc4717adcbc/fish/config.fish https://github.com/LukeChannings/dotfiles/blob/148a5021da464...
- n8henrie 3y ago
  I recently gave a shot to nu + zellij (as a replacement for bash + tmux) recently and had to bail within days due to it breaking my "background the editor in this pane" habit that is pure muscle memory by now.

Any thoughts on fish as compared to nushell [0]? It's similar to PowerShell in its philosophy and is also written in Rust. [0] https://github.com/nushell/nushell https://github.com/nushell/nushell

yencabulator 3y ago

Here's my experience of spending a part of a day with each: Fish: - customizing or debugging Fish's completion was utter torture; the defaults are horrible like "carTAB" completes to "blkdiscard" when I don't have cargo in PATH - nothing in Fish seems to have a useful `--help`, no useful summaries & quick refreshers, just punt the user to a big verbose man page Nushell: - no job control, no background jobs - error handling is utterly broken - control-C breaks unexpected things, what gets aborted seems up to luck (e.g. aborts the prompt building) - globs inside quotes, `ls "*"` - lots of weird parsing errors & bad edge case behavior

hammyhavoc 3y ago
What's your preferred daily driver instead?
- yencabulator 3y ago
  I'm still on bash. I was really hopeful on nushell until I discovered the error handling & control-C -- before those I thought it was "just" lack of job control, now I'm less enthusiastic about the quality.
  - hammyhavoc 3y ago
    Looks like I'll be staying on Bash! It somewhat amuses me that we don't seem to have done better than it in all these years—but I also take a lot of comfort in that. With that said, it still gets updates! So, it can and is still improved. :- ) Hard to compete with such a mature offering.

TheFuzzball 3y ago

I've used Fish for a while (my dotfiles tell me I've been using it for 8 years now... how the time flies! [0]) and decided to give Nu a try. The main problem with Nu is that it can't really be used as a full-time shell because it doesn't support job control, so a lot of nodejs-based CLIs I need for my job seem to lock up the shell. I got around it by using pueue (a daemon that manages processes), but it's clunky to say the least. I do think it'll get better as it matures, but I've been through all that pain with Fish and I'm not sure I want to put myself through that again. [0]: https://github.com/LukeChannings/dotfiles/blob/148a5021da464ec886aff077c6ea1bc4717adcbc/fish/config.fish https://github.com/LukeChannings/dotfiles/blob/148a5021da464...

n8henrie 3y ago
I recently gave a shot to nu + zellij (as a replacement for bash + tmux) recently and had to bail within days due to it breaking my "background the editor in this pane" habit that is pure muscle memory by now.