No, not the <language>, but the unique interface of S3/V4.
What matters is the human-interface. That's what determines
your productivety [maximum gain for minimum pain].
Not needing to switch between awkward F-keys and the screen, and having
easy access to multiple text-files together, and each text-view having
<what the bottle does, written on the bottle, instead of in the filing
cabinet>.
Porting ETHO to linux [both S3 & V4] was a killer app:.
you get the Inet capability of *nix together with the superior
human-interface of ETHO, plus you can view *pdf, LaTex..etc. on the
same screen.
For tricky problems, needing simultaneous views of: email/s,
USEnet/s, your test-logs EHO is unbeaten, especially with the text
colouring facilities, which help extract the meaning of difficult
explanations.
Because opeing/closing a new ETHO-for-linux takes a second, it's
viable to have several copies running in the various dirs, which
are handling current problems. Real life doesn't allow fixing
one problem at a time.
Can those of us who want to escape the WinTel monopoly,
hope to use ARM based CPUs with an ETHO-like interface,
by a porting of the existing/proven code?
== Chris Glur.
PS. LNO's inability to easily navigate the dir-tree, limits its
utility.
