History Main / RapidFireTyping

** They could be using [[UsefulNotes/{{UNIX}} Linux]] and installing software or something--though that does use the space bar a lot. Most shells use Tab for autocomplete, which would circumvent a lot of the space bar use.

* The power of the command line is a major reason why certain people ''love'' the various descendants of UsefulNotes/{{UNIX}}: all of them include very powerful command line tools and shells that let the user combine them in all kinds of ways [[note]]generally by sending the output of one command directly into the input of another, like ''ls -l | grep <some pattern> | more'' (detailed list of files -> filter it down to matching lines -> display results one screenful at a time)[[/note]] to automate basically any task. Using these, a skilled operator can do most of the things a normal person could do through a GUI, but significantly faster, not to mention some things that are ''not'' doable via GUI at all. Rapid-Fire Typing in this environment can be highly detrimental. While the shell is indeed an extremely powerful tool, WithGreatPowerComesGreatResponsibility: the way Unix commands are structured, it's perfectly possible to do serious damage to your data, or even often to the entire system, by making silly typing mistakes that wouldn't even register if you were typing an essay. The old favourite of wiping out the whole drive by ''mistyping a space''[[note]]rm -rf foldername/* removes the contents of the folder, rm -rf foldername /* is the equivalent of "take off and nuke the entire site from orbit"[[/note]] was eventually made impossible to perform by mistake, but it's still perfectly possible to destroy your entire document archive, or instead of copying some files jumbling them up into one huge indecipherable file, or rename things such that their content can no longer be distinguished without going through them one by one. Don't test your typing speed in the shell. And even if you were inclined to, the 'nixes almost all have Tab-autocomplete to save you typing it all out, so you ''should'' be thumping that rather than trying to type out a long file path both manually and at speed.

* In ''Anime/WeissKreuz'', Nagi is seen typing this way... with no hands, using telekinesis.

** Openbox? Pah. Try [[http://dwm.suckless.org dwm]] or any of the [[http://en.wikipedia.org/wiki/Tiling_window_manager tiling window managers]] for [[UsefulNotes/{{UNIX}} Linux/UNIX]].
** dwm? Try ratpoison. It's specifically designed to completely banish the mouse from [=GUIs=] (You can still use the mouse, but all the window management functions and then some are done purely through the keyboard. The mouse is mostly there for apps you run that won't accept any other kind of input, which is, by the way, quite rare in *nix.) and it does a pretty good job of this. dwm is downright mouse-friendly compared to ratpoison. Of course, a great deal of Linux/UNIX fans will sometimes eschew the use of things like the X Window System altogether and do everything, absolutely ''everything'', from a console, including watching movies, thanks to the framebuffer.

* The power of the command line is a major reason why certain people ''love'' the various descendants of UsefulNotes/{{UNIX}}: all of them include very powerful command line tools and shells that let the user combine them in all kinds of ways [[note]]generally by sending the output of one command directly into the input of another, like ''ls -l | grep <some pattern> | more'' (detailed list of files -> filter it down to matching lines -> display results one screenful at a time)[[/note]] to automate basically any task. Using these, a skilled operator can do most of the things a normal person could do through a GUI, but significantly faster, not to mention some things that are ''not'' doable via GUI at all.
** It should be mentioned, however, that Rapid-Fire Typing in this environment can be highly detrimental. While the shell is indeed an extremely powerful tool, WithGreatPowerComesGreatResponsibility: the way Unix commands are structured, it's perfectly possible to do serious damage to your data, or even often to the entire system, by making silly typing mistakes that wouldn't even register if you were typing an essay. The old favourite of wiping out the whole drive by ''mistyping a space''[[note]]rm -rf foldername/* removes the contents of the folder, rm -rf foldername /* is the equivalent of "take off and nuke the entire site from orbit"[[/note]] was eventually made impossible to perform by mistake, but it's still perfectly possible to destroy your entire document archive, or instead of copying some files jumbling them up into one huge indecipherable file, or rename things such that their content can no longer be distinguished without going through them one by one. Don't test your typing speed in the shell. And even if you were inclined to, the 'nixes almost all have Tab-autocomplete to save you typing it all out, so you ''should'' be thumping that rather than trying to type out a long file path both manually and at speed.

* In ''Anime/NeonGenesisEvangelion'', Dr. Ritsuko defeats an Angel turned Computer Virus through this method. That same episode, we see a techie RapidFireTyping away, writing huge amounts of code -- and then Ritsuko comes over and does the same thing ten times as fast, ''with one hand.''

* Done for laughs by an airline clerk in ''Film/MeetTheParents'', with the humor coming from the fact that she employs RapidFireTyping for a straight thirty seconds just to confirm Greg's flight.

* A particularly hilarious example shows up in ''Film/JumpinJackFlash''. Terry, who has just been contacted by a spy while putting in some overtime at her work terminal, engages in a friendly chat with the stranger. She rattles off a few seconds of RapidFireTyping and then [[SoundingItOut helpfully narrates]] her response: "Yo."

* All computers on ''Radio/AdventuresInOdyssey'' require RapidFireTyping (the ones that aren't run by voice command anyway)--not {{justified|Trope}} but understandable, given that it's a radio show and a keyboard generates more sound than a mouse. Later episodes use realistic mouse clicks, although they're still [[BeepingComputers a little loud]].

** It should be mentioned, however, that RapidFireTyping in this environment can be highly detrimental. While the shell is indeed an extremely powerful tool, WithGreatPowerComesGreatResponsibility: the way Unix commands are structured, it's perfectly possible to do serious damage to your data, or even often to the entire system, by making silly typing mistakes that wouldn't even register if you were typing an essay. The old favourite of wiping out the whole drive by ''mistyping a space''[[note]]rm -rf foldername/* removes the contents of the folder, rm -rf foldername /* is the equivalent of "take off and nuke the entire site from orbit"[[/note]] was eventually made impossible to perform by mistake, but it's still perfectly possible to destroy your entire document archive, or instead of copying some files jumbling them up into one huge indecipherable file, or rename things such that their content can no longer be distinguished without going through them one by one. Don't test your typing speed in the shell. And even if you were inclined to, the 'nixes almost all have Tab-autocomplete to save you typing it all out, so you ''should'' be thumping that rather than trying to type out a long file path both manually and at speed.