Seems like a very confusing name for a shell, seeing this without knowing the context I saw 'Oil', 'Shell' and assumed that it was about some oil spill or event with Shell Oil that happened in February I was unaware of. Looks like an interesting project regardless.
I’d say the developer is making their life much more difficult by using such a confusing name, which is a pity because the project looks really interesting.
I use unix (linux) every day, what does Oil fix that is wrong with bash/shell? (I am not a power user per se, so genuinely curious what I am missing out on)
If you want just one example, automatic completion in bash uses a bash parser written in bash, incompatible with the bash interpreter's own parser. OSH uses the same parser for both the interpreter and the completion engine. https://github.com/oilshell/oil/issues/208#issuecomment-4496...
The most interesting part for me is MyPy to C++ conversion. I understand it's easier that way. It certainly makes it easier to package Oil. It's a necessary step to bootstrap all the work. Certainly such a conversion tool would be in interests of wider community, so I wonder is there any more movement in the area.
I have a small hope that it will eventually go off C++, because it may be impossible to change mind of significant part of Unix community. But it's all good, because work involved is outstanding already.
There are interesting posts about the ADSL, as well as about implementing interpreters in that blog. Definitely piqued my interest as someone passionate about language design.
The "Oil Project" was an open-source education initiative run by Marco De Rossi in Italy, ~10 years ago. It turned into WeSchool, a successful education business in Italy.