Skip to content

doc: Remove mention of 30 minute intro #25220

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

Merged
merged 1 commit into from
May 13, 2015
Merged
Changes from all commits
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
17 changes: 8 additions & 9 deletions src/doc/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,15 +5,14 @@ to jump to any particular section.

# Getting Started

If you haven't seen Rust at all yet, the first thing you should read is the [30
minute intro](intro.html). It will give you an overview of the basic ideas of Rust
at a high level.

Once you know you really want to learn Rust, the next step is reading [The
Rust Programming Language](book/index.html). It is a lengthy explanation of
Rust, its syntax, and its concepts. Upon completing the book, you'll be an
intermediate Rust developer, and will have a good grasp of the fundamental
ideas behind Rust.
If you haven't seen Rust at all yet, the first thing you should read is the
introduction to [The Rust Programming Language](book/index.html). It'll give
you a good idea of what Rust is like.

The book provides a lengthy explanation of Rust, its syntax, and its
concepts. Upon completing the book, you'll be an intermediate Rust
developer, and will have a good grasp of the fundamental ideas behind
Rust.
Copy link
Member

Choose a reason for hiding this comment

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

to reduce awkward repetition: "behind Rust" -> "behind the language"

I'd go as far as removing the "you'll be an intermediate Rust developer"

I'm also wondering if "explanation of Rust" excludes Rust concepts, and I wonder if there's a need to mention that the book will also talk syntax (obvious). I'd trim things so that we'd have something like:

If you haven't seen Rust at all yet, the first thing you should read is the introduction. It'll give
you some idea of what Rust is like. The book will explain the language in much greater detail. You should have a good grasp of the fundamental ideas upon completing it.

Copy link
Contributor

Choose a reason for hiding this comment

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

to reduce awkward repetition: "behind Rust" -> "behind the language"

👍

I'd go as far as removing the "you'll be an intermediate Rust developer"

👍

My suggested wording for that paragraph

If this is your first encounter with Rust, the first thing you should read is the introduction. It'll introduce you to the syntax, the primary motivations for creating Rust, and how to set up your own Rust development environment. The rest of the book will explain the language in much greater detail and upon completing it you should have a good grasp of the fundamental ideas behind the Rust programming language.

Copy link
Member

Choose a reason for hiding this comment

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

Very nice improvement, but we got to have a pause:

..much greater detail, and upon completing...

Copy link
Member

Choose a reason for hiding this comment

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

@brson, what do you think? I don't feel strongly that this paragraph needs updating, but I don't mind @echochamber 's version either.


[Rust By Example][rbe] was originally a community resource, but was then
donated to the Rust project. As the name implies, it teaches you Rust through a
Expand Down