When comparing eltclsh vs mksh (MirBSD Korn Shell), the Slant community recommends mksh (MirBSD Korn Shell) for most people. In the question“What are the best Bash replacements?” mksh (MirBSD Korn Shell) is ranked 10th while eltclsh is ranked 11th. The most important reason people chose mksh (MirBSD Korn Shell) is:
mksh is very light on resources it needs to use and as a result it's quite fast. It also gets better results consistently than other alternatives when comparing benchmarks.
Ranked in these QuestionsQuestion Ranking
Pros
Pro A more consistent alternative to the POSIX shell
Tcl is a saner scripting language built on the same principle as the Unix shell (everything is a string) with more than a hint of Lisp. eltclsh makes it possible to use Tcl interactively with tab completion for both language constructs and file paths. The result is that you can develop a snippet of Tcl code interactively and then paste it in your script.
Pro TclVFS
TclVFS allows you access files inside ZIP archives or on remote HTTP and FTP servers like you would local files. If you put "package require vfs::urltype; vfs::urltype::Mount http"
in your ~/.eltclshrc you can do things like "file copy http://example.com/file /tmp/file" (HTTPS is currently not supported by TclVFS.)
Pro Very fast
mksh is very light on resources it needs to use and as a result it's quite fast. It also gets better results consistently than other alternatives when comparing benchmarks.
Cons
Con Stability
eltclsh crashes on mismatched delimiters.
Con Development is pretty slow
Mksh is part of MirBSD which is barely even being developed anymore nowadays.