I find rc shell to be much more logical than a normal sh, but nowadays it's only used by a few people, so for the new users there is little sense of learning it

I find rc shell to be much more logical than a normal sh, but nowadays it's only used by a few people, so for the new users there is little sense of learning it - most people haven't even heard of rc! I think that are two ways to change this situation: 1) For normal CLI users - let's pick the most up-to-date implementation (tobold's rc, es, inferno's sh, suckless' rc...) or write one from scratch if that would be easier. Then think about writing plugins for git, for colorful prompts, for autocomplete, for common development tasks etc. Since rc language is easier and cleaner than bash - writing plugins and extensions for it should be easier. Of course, many blog posts must be written showing how superior it can be comparing to bash in some cases and how easier it is to learn. Once the resulting rc gets into every linux distro and mac and there will be known repositories like ohmyzsh - people may start switching from bash to rc, not from bash to zsh. 2) For embedded systems - from my experience sh scripting is normally done not for the desktop, but for tiny embedded systems, where busybox is a definite winner - maybe an alternative can be made by using rc shell and Plan 9 set of utilities? So we get a single static binary (again, rewrite rc in Go?) and a small set of tools, that might even work on windows. I think it could be smaller, like toybox, but with a usable shell interpreter. Since most implementations of rc are now unmaintained (correct if I'm wrong) - probably it would be better to rerite it in some modern language (Go, Rust, maybe C++), cover with tests and start promoting it. If so - I would be happy to join the development (I started it once, ended up with just yacc-generated AST parser, but I though it might become a huge project that nobody is interested in, so I suspended the development).