I think the key difference between GCLI and TermKit / JSShell is this:
"TermKit is not a... ...Reimplementation of the Unix toolchain. It
replaces and/or enhances built-in commands and wraps external tools."
(from https://github.com/unconed/TermKit)
GCLI's primary purpose has always been embedding in something other than
a shell. This means that all the commands are custom written, which
means we can have opinions about how they should be written rather than
having to suck up the mess of tar/ls and make sense of it. I don't know
that it makes sense to make a shell of GCLI, especially if it's being
done well elsewhere.
At some stage I'd be interested to debate pipes and their use in
non-resource constrained systems. But maybe the place for that is over a
beer, not over a shiny new mailing list :) The difference may come down
to the point above anyway.
FWIW, we very much hope that GCLI will soon be relicensed from
GPL/LGPL/MPL to something broader. So if there is a need to share code,
we can better.
Joe.