B. Stroustrup once inferred that C++ is a language, whereas in the Lisp or Smalltalk world, coders commonly try to provide a complete environment for programming in use, furthermore in describing a language's characteric, as in C++, if you are working on a UNIX system, C++ will sound, or feel, like a UNIX language, and if on the other hand you are working under DOS, it will feel like a DOS language.
https://www.youtube.com/watch?v=69edOm889V4&spfreload=10
The Design of C++
17:39 minutes into the video - 1994
If one maintains the view that the motivation of the coders for work listed on the cited cat-v webpage was to have accessible 9P for use on GNU/Linux, that such labour hours were soley pursued predating the release of the Linux kernel version 2.6.14 (on 27 October 2005), with its v9fs (http://v9fs.sourceforge.net/),† or otherwise delegated to coding languages' exercises and "proof of concept" endeavours, and, that Lisp coders' provision of an environment is complete, and, Elisp coders dispute the first paragraph's description of a language, then, I guess, the position of RMS is correct.
https://9p.io/wiki/plan9/v9fs/index.html
† The word Wiki points to a dead link.
Sent: Wednesday, December 19, 2018 at 6:21 AM
From: "Paul Eggert" <address@hidden>
To: "Eric Lindblad" <address@hidden>, address@hidden
Subject: Re: Elisp 9P?
Eric Lindblad wrote:
> "It makes no sense to put this feature into Emacs, which is the wrong place for
> it. The right place for it is in the kernel (Linux or the Hurd), so that all
> the application programs will be able to use it."
This sounds reasonable. v9fs has been in the Linux kernel since 2.6.14 and that
should let GNU/Linux application programs use 9P without modification. So why
would we want to modify apps like Emacs to implement 9P separately? What am I
missing here?