This doesn't seem like it's true. I feel like it came from the unix culture. Unless they got it from drug dealers...
This doesn't seem like it's true. I feel like it came from the unix culture. Unless they got it from drug dealers...
> And o there is this incredible remark which a guy from Wired told me, that there are only two industries which refer to their customers as users, drugs and computers. "I've just got to have release 7.2", right!
Oddly relevant to social media nowadays though.
That's part of why the metaverse is such dystopian bullshit. Like I need my entire field of view taken away too, so Lord Zuck can sell more ads? Ew, gross, no.
I am struggling to find a source for who first called users "users" back in 1967 - Actually I see it being used in the 1965 "Multics" papers [0] and the 1964 article in The Atlantic "Computers of Tomorrow" [1], as if it was already a term-of-art.
1950 Science 112 732/1 Analog machines..are enthusiastically supported by their users.
1959 E. M. McCormick Digital Computer Primer x. 139 The number of instructions which can be executed by a computer represents a compromise between the designer's and user's requirements.
I'm tempted to pick up a copy of Digital Computer Primer on ebay, I love the old explanations of what these machines even are.
151 "user" jargon "The Jargon File (version 4.4.7, 29 Dec 2003)"
user
n.
1. Someone doing "real work" with the computer, using it as a means rather than an end. Someone who pays to use a computer. See {real user}.2. A programmer who will believe anything you tell him. One who asks silly questions. [GLS observes: This is slightly unfair. It is true that users ask questions (of necessity). Sometimes they are thoughtful or deep. Very often they are annoying or downright stupid, apparently because the user failed to think for two seconds or look in the documentation before bothering the maintainer.] See {luser}.
3. Someone who uses a program from the outside, however skillfully, without getting into the internals of the program. One who reports bugs instead of just going ahead and fixing them.
The general theory behind this term is that there are two classes of people who work with a program: there are implementors (hackers) and {luser}s. The users are looked down on by hackers to some extent because they don't understand the full ramifications of the system in all its glory. (The few users who do are known as real winners.) The term is a relative one: a skilled hacker may be a user with respect to some program he himself does not hack. A LISP hacker might be one who maintains LISP or one who uses LISP (but with the skill of a hacker). A LISP user is one who uses LISP, whether skillfully or not. Thus there is some overlap between the two terms; the subtle distinctions must be resolved by context.
.
151 "user" foldoc "The Free On-line Dictionary of Computing (30 December 2018)"
user
1. <person> Someone doing "real work" with the computer, using it as a means rather than an end. Someone who pays to use a computer. A programmer who will believe anything you tell him. One who asks silly questions without thinking for two seconds or looking in the documentation. Someone who uses a program, however skillfully, without getting into the internals of the program. One who reports {bugs} instead of just fixing them. See also {luser}, {real user}.Users are looked down on by {hackers} to some extent because they don't understand the full ramifications of the system in all its glory. The term is relative: a skilled hacker may be a user with respect to some program he himself does not hack. A LISP hacker might be one who maintains LISP or one who uses LISP (but with the skill of a hacker). A LISP user is one who uses LISP, whether skillfully or not. Thus there is some overlap between the two terms; the subtle distinctions must be resolved by context.
2. <jargon> Any person, organisation, process, device, program, {protocol}, or system which uses a service provided by others.
The term "{client}" (as in "{client-server}" systems) is rather more specific, usually implying two processes communicating via some protocol.
[{Jargon File}]
(1996-04-28)
.