Command Line

Introduction

To date, most of your computer experience has been using graphic user interfaces (GUI, pronounced like “gooey”). This is a visually intuitive way to interact with your computer using your mouse, trackpad and/or keyboard.

In fact, GUIs are so common, you may wonder: are there other user interfaces for computers? If you’ve ever spoken to your computer, phone or other device – saying, “Hey, Google” or “Hey, Siri” – then you’ve used a voice user interface.

Graphic and voice user interfaces are both new additions, however. The original computer interfaces were wholly text based – the prompts provided by the computer were in text and user input was entirely typed commands.

While GUIs have largely replaced text-based computer interfaces, they are still used and useful.

Why use the CLI

Images of the command line interface (or CLI) in popular media are often tied to hacking – like in The Matrix or Mr. Robot – but there are common legit reasons to use the command line, too.

While GUIs are far more intuitive, the command line can be faster and allow for greater customization and automation.

Many developer tutorials expect some degree of familiarity with the command line. So, while it may be a bit intimidating to start with, it’s worth tackling. This course won’t provide an in-depth overview of the CLI, but you will use it for interacting with git and GitHub.

Both VS Code and Glitch have an integrated command line, which is called Terminal or sometimes Console.

While there are some technical differences between a terminal, a console, and the command line, they’re not important to get into at this point. Going forward, the class documents will always refer to console, since that’s the name used in for the Glitch terminal inside of VS Code. 👍🏻

Learn more about the:

• VS Code TerminalFollowing and reading this link is optional.✳️

• Glitch TerminalFollowing and reading this link is optional.✳️