🚀 go-pugleaf

In several years of daily use of the MKS Toolkit, I have only run into
one bug in the toolkit and when I reported that to MKS, they sent me a
fixed version of KSH at no cost within 10 days.  I would be more inclined
to believe in bug reports if they were detailed -- a posting which just
says there are lots of bugs without detailing them is less credible to me.

I found one case where there was a bad interaction between KSH and the
RAF software used to network my PS/2 to a VMS cluster.  MKS Tech Support
was really helpful to me in isolating what was happening and understanding
how their implementation expected things to work.  I eventually got the folks
who make the RAF software to acknowledge that it was their software (i.e. not
MKS's software) that had the bug.

People who are used to CSH will find using KSH awkward, but on our UNIX
systems here the KSH (ksh88b is the version) has all of the capabilities
of CSH (as distributed with 4.3-Tahoe BSD) including history and job control.
Certainly VI and EMACS users will prefer the KSH history mechanism.  
Your milage will vary.  Further discussion of shells probably belongs
in comp.unix.shells

I have no affiliation with MKS other than as an ordinary (very satisfied)
customer.