Content deleted Content added
→Command-line interpreter conflates shell with CLI: logical backspace |
→Prevalence: About half a decade until initial adoption |
||
Line 713:
:And if you're spending most of your time on the computer typing into a Web form, is that the GUI under which the browser is running, or is it "3270 for the '90's", as I think somebody may have called web forms?
:I'd say that "the narrow context of operating systems" corresponds to users using a "computer" rather than using a particular application. For example, somebody working on a scientific paper might use a language processor to develop a program to do modeling, analyze data, etc. (or use an existing program for that), use text editor/text formatters/word processors to write up the paper, and email to communicate with colleagues and scientific journals; most of them probably used a CLI, at least in the pre-GUI era. Somebody at a travel agency might be communicating with one particular backend program from their terminal, without using a CLI, although, nowadays, they might be using a GUI with the Web browser being used to communicate with backend programs to make reservations and using a mail program to communicate with clients etc.. [[User:Guy Harris|Guy Harris]] ([[User talk:Guy Harris|talk]]) 20:00, 1 August 2025 (UTC)
::Yes, in the half decade from the [[IBM 701]] and [[UNIVAC I]] until the first monitors it was all manual loading of cards and tapes for individual jobs; even after it took a while for monitors to gain traction.
::By the 1970s there were a lot of applications using, e.g., [[IBM 2260]], [[IBM 3270]], for applications like reservations. SPF and its competitors were edging out cards and hardcopy terminals for editing. PROFS was huge. This was all formatted text screens with multiple entry fields. A clerk using [[Programmed Airline Reservations System|PARS]] to book a flight wouldn't recognize a command line if it hit him in the nose.
| |||