Skip to content

Commit

Permalink
Updates based on comments
Browse files Browse the repository at this point in the history
  • Loading branch information
Robinlovelace committed Mar 24, 2023
1 parent 18401c8 commit 0b9e06f
Showing 1 changed file with 3 additions and 4 deletions.
7 changes: 3 additions & 4 deletions 10-gis.Rmd
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,7 @@ library(gdalcubes)
## Introduction

A defining feature of [interpreted](https://en.wikipedia.org/wiki/Interpreter_(computing)) languages with an interactive console --- technically a read-eval-print loop (REPL) --- such as R is the way you interact with them:
rather than relaying on a pointing and clicking on different parts of a screen, you type commands into the console and hit `Enter` each time you want a command to be executed.
rather than relying on pointing and clicking on different parts of a screen, you type commands into the console and execute them with the `Enter` key.
A common and effective workflow when using interactive development environments such as RStudio or VS Code is to type code into source files in a source editor and control interactive execution of the code with a shortcut such as `Ctrl+Enter`.
In other words, R is typically controlled by a command-line interface (CLI)\index{command-line interface}.

Expand All @@ -37,10 +37,9 @@ According to the creator of the popular QGIS software [@sherman_desktop_2008]:

> With the advent of 'modern' GIS software, most people want to point and click their way through life. That’s good, but there is a tremendous amount of flexibility and power waiting for you with the command line. Many times you can do something on the command line in a fraction of the time you can do it with a GUI.
'CLI vs GUI' debate does not have to be adverserial: both have advantages.
Which is most appropriate depends on a range of factors including the task (with drawing new features being well-suited to GUIs), the level of reproducibility desired, and the user's skillset.
The 'CLI vs GUI' debate does not have to be adverserial: both ways of working can have advantages, depending on a range of factors including the task (with drawing new features being well-suited to GUIs), the level of reproducibility desired, and the user's skillset.
GRASS is a good example of GIS software that is primarily based on a CLI but which also has a prominent GUI.
Likewise, while R is focussed on its CLI, IDEs such as RStudio provide a GUI for improving accessibility.
Likewise, while R is focused on its CLI, IDEs such as RStudio provide a GUI for improving accessibility.
Software cannot be neatly categorised into CLI-based or GUI-based.
However, interactive command line interfaces have several important advantages in terms of:

Expand Down

0 comments on commit 0b9e06f

Please sign in to comment.