Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add barebones "First Steps" to the GNU/Linux page #19

Merged
merged 3 commits into from
Feb 16, 2018
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions gnu-linux/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,6 +3,12 @@ layout: page
title: GNU/Linux
---

# First Steps
There are many different linux distros, but this guide is going to cover Ubuntu, which is one of the most common ones. The first thing you're going to need is the `build-essential` package, which contains the `gcc` and `g++` compilers, as well as the common build tool `make`. In order to do this, simply run (on the command line) `apt-get install build-essential`.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit: we try to be fair in giving credit, so call it GNU/Linux instead of linux.


# Editors
If you're planning to write code, you're going to need a way to edit files! If you enjoy working on the command line, we'd recommend either `vim` or `nano`, while if you prefer a GUI, we recommend either [Atom](https://atom.io) or [Brackets](https://brackets.io).
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm this is an interesting direction -- we've never talked about editors on StartHacking, but I guess it is an essential that we've completely missed so far! I think the best way to approach this heavily opinionated topic is use wording along the lines of "most popular" or "common" rather than "we recommend".

Inserting my personal opinion, I think we should be listing vim and emacs rather than vim and nano. I think emacs is more popularly used than nano for software engineering.

In terms of phrasing the two types of options, I'd start by suggesting Atom or Brackets as common graphical editors (maybe even explain this means using a mouse), and list vim and emacs as more advanced, purely keystroke based editors for when you become comfortable coding.

Minor edits:

  • "GUI" is jargon -- please change it to "graphical interface" or something similar

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yup, I agree. nano is just the second editor that came to mind as I was writing this. Would it potentially make sense to make a separate page talking about editors, as the vast majority of are cross-platform?


# Getting Started with [x]

{% for post in site.posts %}
Expand Down