

Nothings bad about it. I don’t think it’s strictly better or worse. Just
- I’m used to it
- The comparison in the video was just disingenuous.


Nothings bad about it. I don’t think it’s strictly better or worse. Just


I get annoyed by differences with (Ba|Z)sh when I try Fish, but nushell is so much its own thing that it’s fun.


Scrubbing through the video, this hurts my soul
echo $(echo $STRING | sed 's/World/Bash/')
For variables bash has PE forms:
echo ${STRING/World/Bash}
I miss these too much when I try Fish.


string split/collect and similar can’t work unless its a builtin. The set foo ( ...... | string ... ) pattern couldn’t work if string was an external binary.


Steam has always had a Linux Runtime for that exact reason.


I’ve always considered it to be such that the whole thing is simultaneously a joke and true (haha jk, unless?), or maybe just hyperbole. But I’ve avoided using it myself because clearly it gets misinterpreted way too frequently
Not as cursed as
print("eovdedn"[n%2::2])


I don’t fit into any of those categories.
Its obtuse, old, and doesn’t have a lot of functionality of modern code editors
Obtuse? Yeah. The keyboard focus means natural discoverability is low. But I immediately preferred modal editing once I learned it.
Old? Eh, most people use Neovim nowadays and write plugins in lua. Even in OG Vim, Vim9script broke compatibility for a better dev experience.
Functionality? Out of the box, it is just a text editor. But only VSCode might have a more active plugin ecosystem. ALE has been a thing for ages if it’s LSP support you’re looking for.
It’s not better, it’s not worse, I’m not in any way superior for using it, but I love it for a reason.
Single quotes don’t allow any escaping in shell, you need
'I don'\''t know what you mean, I'\''ve never encountered any annoyances'Or, in Zsh with
setopt rcquotes:'I don''t know what you mean, I''ve never encountered any annoyances'