Why Create a New Unix Shell?
11–20 of 63 posts
Re: Why Create a New Unix Shell?
#12Re: Why Create a New Unix Shell?
#13I think the author realized something important. There's the bash as a CLI users and bash as a scripting language users. I'm firmly in camp one and I think it's an important difference to realize. I don't want my CLI to be a REPL for a scripting language. It's something I really disliked about PowerShell when I tried it. It just felt like a dotnet scripting language and not like a CLI. If Oil provides a scripting int…
Re: Why Create a New Unix Shell?
#14I think the author realized something important. There's the bash as a CLI users and bash as a scripting language users. I'm firmly in camp one and I think it's an important difference to realize. I don't want my CLI to be a REPL for a scripting language. It's something I really disliked about PowerShell when I tried it. It just felt like a dotnet scripting language and not like a CLI. If Oil provides a scripting int…
Re: Why Create a New Unix Shell?
#15> GNU bash is the most popular shell implementation in the world. It was first released in 1989, and implements the POSIX standard plus many extensions. It's the default shell on most Linux distributions, runs on BSD Unix variants, used to ship on Mac OS X, and runs on Windows. Note that macOS still ships bash.
Re: Why Create a New Unix Shell?
#16> GNU bash is the most popular shell implementation in the world. It was first released in 1989, and implements the POSIX standard plus many extensions. It's the default shell on most Linux distributions, runs on BSD Unix variants, used to ship on Mac OS X, and runs on Windows. Note that macOS still ships bash.
I haven’t had a Mac in a few years but iirc they ship zsh* nowadays not bash
Re: Why Create a New Unix Shell?
#17Re: Why Create a New Unix Shell?
#18It's only tangential but switching to fish shell made me about 3 times more productive. Being able to easily recall commands, to have completions displayed as I type, and to have interactivity be a first class citizen of the environment... made working in the shell so so so so much nicer. Fish has its own quirks, some of which seem unnecessary, but it was a godsend. There is definitely still room for improvement of t…
I write maybe a few dozen lines of code on a good day.
Re: Why Create a New Unix Shell?
#19I think the author realized something important. There's the bash as a CLI users and bash as a scripting language users. I'm firmly in camp one and I think it's an important difference to realize. I don't want my CLI to be a REPL for a scripting language. It's something I really disliked about PowerShell when I tried it. It just felt like a dotnet scripting language and not like a CLI. If Oil provides a scripting int…
What if the language is “shell”-ish? Reading the piece, the idea of shell as a REPL seemed attractive.
But powershell e.g. prints errors that look like stacktraces (it's been a few years i don't remember exactly) with type information. And while that may be desirable to some, when using bash i'm using a UI as a user and not programming and i don't want to read a stacktrace. I want an error message in english telling me what's wrong.
Re: Why Create a New Unix Shell?
#20> GNU bash is the most popular shell implementation in the world. It was first released in 1989, and implements the POSIX standard plus many extensions. It's the default shell on most Linux distributions, runs on BSD Unix variants, used to ship on Mac OS X, and runs on Windows. Note that macOS still ships bash.
I haven’t had a Mac in a few years but iirc they ship zsh* nowadays not bash