At one point, Kermit (the protocol) was kind of the <i>lingua franca</i> of file transfer. The computing world was much more heterogeneous back then. Fun times.<p><a href="https://en.m.wikipedia.org/wiki/Kermit_(protocol)" rel="nofollow">https://en.m.wikipedia.org/wiki/Kermit_(protocol)</a>
There's some nice complaints about the difficulties of doing (really) long-term software development.<p>"Unix and C badly need a "stability layer" to keep programs working over the long term."<p>""Dangling else" is (or was) perfectly legal when used correctly; the C language was originally designed for use by people who knew what they were doing .... It makes no sense to keep changing this or any other programming language out from under all the millions of programs that have already been written in it."<p>"In my view it is a CRIME to change an API for any reason when unknown numbers of programs depend on it, and unknown numbers of people depend on those programs."<p>"What I don't understand is how large segments of the world's economy can be based on software written in a language that keeps changing out from underneath it."
I used ckermit on Coherent years ago to log into work. Then work would dial back and allow me to connect to avoid phone charges. good times :)<p>I even purchased the book to support the project, it had lots of cool info in it.<p>Eventually I compiled it for Linux when mark Williams closed. I have not had a need for it these days, will need to see if I can do anything I can use it for.