Things you most definitely can’t live without are an interactive shell (aim for something modern with convenient tab-completion) and a text editor. If you want to become a console dweller, you need to equip yourself with a minimum set command line developer tools-the bare essentials. Probably the most famous one is Midnight Commander (mc), a clone of extremely popular (in the 90s) Norton Commander. (“Are you sure you want to proceed with the installation from unverified source?”) Then, there are textual user interfaces (TUIs), which are interactive GUI apps designed to fit the limitations of a terminal. There are interactive or semi-interactive interfaces most often found in package managers. There are non-interactive ones like ls, which simply take the parameters and provides the output. It is worth knowing that a terminal tool can offer several types of interfaces. As usual, we rely on computers to handle tasks humans may find boring, repetitive, or overwhelming. What’s more, performing the same operations manually introduces both an added cognitive load and the increased possibility of human error. The problem is, this still won’t beat the efficiency of a specialized script. You can get better at doing repetitive tasks in GUI, to the point that your multiple clicks are heard as a single long one. Knowing CLI commands and using quality tools can make you more productive and can also open doors to various approaches to automation that are far more practical with textual interfaces than with GUI apps. This article focuses on the practical side of using command line interface (CLI) tools. Why We Still Use Command Line Interface Tools However, in the real world, command line tools aren’t used for their entertainment value.
Such representations of hackers in action are often mocked by professional developers, and there are even some programs that simulate various “hacker” effects, just for fun.
0 kommentar(er)
