The project has two sides: a lot of it is about running existing programs and improving the language (OSH), but there is also an upgrade path into a new languag

The project has two sides: a lot of it is about running existing programs and improving the language (OSH), but there is also an upgrade path into a new language Oil: http://www.oilshell.org/release/latest/doc/oil-language-tour.html 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 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/ 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 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-parts#shell-the-good-parts https://www.oilshell.org/blog/tags.html?tag=shell-the-good-p...