Software Consultant & Developer at Atomic Object Grand Rapids. Loves a good refactor.
Landed here while researching on how people usually run fish+nvm on macOS :)
Fish is awesome, indeed, I’ve been using it for a long time. Did you know about Elvish?
https://elvish.io / https://github.com/elves/elvish
While I believe it has a great potential I’ll stick to Fish for now because bobthefish <3
Btw, you might as well may want to check out:
https://github.com/i90rr/fnm (Node version manager fish-native)
I like Fish too but stopped using it because of fish and Bash differences you mentioned
I hate so much shell scriptings. Because of its limitations and weirdoes. Like Bash: if:fi case:esac; and …no floating points! The only useful (posix?)syntax are “command && success-code || fail-code” – But Fish 3.0 introduces it :)
And I don’t understand why the world is complaining against Fish that is supposedly not posix… But try run a foreign shell script in a given shell without subshell’ing in that foreign shell… Duh!
In Fish :
No weird keywords. Just like any “NORMAL” programming languages.
But all shells no exceptions : Inputs from stdin: Keyboard is very, very limited. No real Control-Keys support. ( arrow keys, function keys, etc. CTRL-[xxx]; shift-[xxx]; alt-[xxx]-super-[xxx]) – System programmers are too lazy to handle inputs from physical device versus terminal TTY controls commands.
In 2019, there is two kind of interractive comm : Keyboards and Mices and now EVERY CLIENTS run on real computers with at least a phsysical keyboard attached. No more “Virtual TTY”. Fish does not escape it. So Fish is as interactive as Bash and co. => NOT SO!
Thanks :) Hehehehehe!
Comments are closed.
We’d love to talk with you about your next great software project. Fill out this form and we’ll get back to you within two business days.