The standard shell experience is decades old, and makes it cumbersome to keep up with the pace of today. The appeal of zsh/fish is the user experience and extensibility. I have a shell config using zinit [^1] that installs my dev environment for me (fzf, tmux, nvim, and my zsh-plugins) as long as zsh exists on the new machine. While one may argue that they prefer strictly standard bash so that everything is POSIX compliant, you just have to ensure that your scripts are run with bash or whatever shell the script was made for.
Because I forget. Because some scripts are run from others. Because I don't want to check the shebang of every script I run.
I would probably deal with the annoyance if I could see a really compelling reason to switch.
>The standard shell experience is decades old, and makes it cumbersome to keep up with the pace of today.
Supposedly but the features I'm missing out on seem to either be cosmetic or something I've been doing in bash for years.
>I have a shell config using zinit [^1] that installs my dev environment for me
I have something similar in bash.
http://www.oilshell.org/release/latest/doc/oil-language-tour...
The OSH part is mature, but the Oil part is less mature, which is why there is more written about OSH. (Yes it's a bit confusing that the whole project is called Oil, and it contains a part called the Oil language.)
----
I need to write a blog post about it, but basically ALL my Python programs are driven by shell scripts, and it saves a ton of code.
The oilshell.org website (which is bigger than it seems) is written this way: http://www.oilshell.org/site.html
All the tests and benchmarks are written this way, links here: https://www.oilshell.org/release/0.9.4/
There are a lot of examples in the benchmark/, test/, build/, etc. dirs: https://github.com/oilshell/oil/tree/master/benchmarks
Factoring into processes is an important design skill. It lets you write a lot less code and thus create more reliable and stable systems. It's basically policy vs. mechanism, or control plane vs. data plane. These are very important but seems to be out of fashion for some reason. So yeah I have been behind in writing about them, but there are some under #shell-the-good-parts
https://www.oilshell.org/blog/tags.html?tag=shell-the-good-p...
I am curious about oil but I found the "why use oil shell" explanation also slightly underwhelming. I'm also a bit concerned that its sales pitch seems to be almost entirely about "fixing" bash so that it is a better/stricter language. This is setting off alarm bells in my head coz it sounds like the exact same merry go round as last time.
Like the author I heartily agree bash is a shit language and I'll never use it to script anything over 25 SLOC, but the shell is so embedded at this point that I'm loath to switch unless there are some really big wins and/or the transition is seamless. I'm unconvinced of either in this case.
I do get the sense that there's some depth to this shell that isn't readily apparent from a surface glance and there is a lot that has been very carefully thought out, but whether that translates into some notion of "abstract language purity" or something that will actually benefit me on a day to day basis isn't clear.
I also don't quite get this:
>Why not use only Python? Because I'd rather write 100 lines of shell + 100 lines of Python than 500 lines of Python. This is basically the Unix Philosophy, and I didn't understand it until after I'd been programming for many years.
I don't think I've ever written a python program that could be decomposed into 100 lines of shell + 100 lines of python. I'm curious as to what kind of example the author had in their head when they wrote this.
In general I find python programs to be no longer than an equivalent shell, safer and often shorter, largely thanks to the library ecosystem.