> But we could imagine a shell that understands webassembly, and hence we can use it with many languages. We could even imagine tools to inline webassembly gene

> But we could imagine a shell that understands webassembly, and hence we can use it with many languages. We could even imagine tools to inline webassembly generation, so that you can code directly in your favorite language in the shell, and it gets transparently compiled and executed. For a shell as an interactive command interpreter, I don't see the point of it. For the shell as a programming language, you can already use any other language in its place. > I wish there were a terminal that behaves more like a file browser, with back and next button, an address bar, and a way to temporarily switch the view from text to icons to select files with the mouse then enter a command for thoses. Some file operation should also be available from a right click on a file path. This sounds more like the domain of a shell than a terminal. A terminal has no concept of what's generating the stream of control codes. A shell on the other hand could easily implement functionality like this.