The Janet Language
One thing that bothers me about languages that compose functions like this <i>f(g(x))</i> is that when programming interactively <i>f</i> is typically an afterthought.  So, you start out with <i>g(x)</i> and then need to go all the way back and add <i>f</i>.  Similarly, when <i>x</i> turns out like it needs to be elaborated, and you either have to go all the way back, or edit the expression in place making it longer and inevitably facing problems with terminal length and terminal input being determined by when you press "Enter".<p>I like Lisp languages, and would take Scheme over Python for my job in a heartbeat, if I was allowed to.  But, I think, that if we want interactive Shell-like programming, we really need to address the issues above in the language.  Shell pipes are a good start, but they are quite restricted in what they can do and require xargs "extension".  Some languages also have the "where" form, where arguments to a function can be elaborated after the function call.<p>If I was ever to design a language for interactive programming, I'd certainly try to have these two features in it.