Hacker News Reader

Comment by vasergen | Hacker News Reader

I like software where you don't need to spend hours or even days on configuration and it just works out of box. Unfortunately the different syntax is no go for me. I have a bunch of scripts which I can run on my local machine and remote interchangeably. Even if syntax is better I want to learn rather `one syntax` that work everywhere. But that is only one thing that prevents me from trying it.

View on HN

Maybe it’s a personal quirk but all of my shell scripts have a shebang (#!) header anyway.

I’ve used fish as my shell for years and still have so far never written any shell scripts in fish. It may also be a nice scripting language, but I personally use it because it’s a fantastic interactive shell.

Mine even have a #!/usr/bin/env which I never shook due to going back and forth between Linux and FreeBSD at one point (bash isn't where you might expect).

I think i'd be up for trying out a new shell for my command line, it's rare I use shell specific syntax heavily for one liners... unless I just don't know it yet.

Just add #!/usr/bin/env bash?

Just invoke your scripts with sh or bash

I basically always do that anyway. I never get around to working them executable so I just do

bash foo.sh

Which is actually easier to type than

./foo.sh

Especially as you can probably just type 'foo' followed by up arrow

Agreed. Wish there was a pretty shell like fish that used /bin/sh under the hood.

Reply on news.ycombinator.com