> There is nothing about the context of Unix that makes this use case different than any other. I disagree; the programs which make up a Unix-like system are d

> There is nothing about the context of Unix that makes this use case different than any other. I disagree; the programs which make up a Unix-like system are designed to be modular (even extremely so, compared to {say} Windows), which greatly facilitated the development of GNU, a replacement for Unix. "As the GNU Project's reputation grew, people began offering to donate machines running Unix to the project. These were very useful, because the easiest way to develop components of GNU was to do it on a Unix system, and replace the components of that system one by one...it was legitimate to use a proprietary package when that was crucial for developing a free replacement that would help others stop using the proprietary package...Today we no longer have any copies of Unix, because we have replaced them with free operating systems." --from https://www.gnu.org/gnu/thegnuproject.html https://www.gnu.org/gnu/thegnuproject.html > With your reasoning we are all using C no matter if we've never seen the language at all Well, we kind of are. For example: if we haven't replaced all our copies of libc by 2038 with one that supports dates after 2038, then we're all screwed. Whether or not we 'personally' use C or not. > Janet Well, skipping over the fact that I don't know anyone named Janet (;-D) I'd say "Janet's downstairs, let me get her for you."