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

doc/tour: write more tours #4659

Open
gopherbot opened this issue Jan 14, 2013 · 8 comments

Comments

@gopherbot
Copy link

commented Jan 14, 2013

by jimmyok@google.com:

The go lang tour expects coding experience in a previous language, with comments like
"type does what you would expect" 

I think for someone with little to no previous coding experience the tour would be next
to impossible to finish. There are also a lot of examples with complex mathematical
operations, such as re-writing sqrt and Fibonacci for experienced programmers this would
be fine, but If I was trying to get a member of my family to go through the tour they
would probably leave at that point.
@bradfitz

This comment has been minimized.

Copy link
Member

commented Jan 15, 2013

Comment 1:

There have been discussions about different tours for people coming from different
backgrounds.  You can imagine a "Go for C++ programmers" tour vs "Go for Python
programmers" vs "Go for new programmers".
Such content hasn't been written yet.
@rsc

This comment has been minimized.

Copy link
Contributor

commented Jan 15, 2013

Comment 2:

I'll leave this open for the more general problem of writing more tours for people from
different backgrounds. It is definitely true that the current tour assumes you can
program in some other language already. An intro to Go for people who have never written
a program before would be great but it's also quite a bit more difficult than an intro
to Go for people who already know the basics of programming.

Labels changed: added priority-someday, removed priority-triage, go1.1.

Status changed to LongTerm.

@rsc

This comment has been minimized.

Copy link
Contributor

commented Jul 30, 2013

Comment 3:

Labels changed: added go1.2.

@ianlancetaylor

This comment has been minimized.

Copy link
Contributor

commented Sep 7, 2013

Comment 4:

Remove Go1.2 tag; this should be done but it's not a release issue.

Labels changed: added priority-later, removed priority-someday, go1.2.

@rsc

This comment has been minimized.

Copy link
Contributor

commented Nov 27, 2013

Comment 5:

Labels changed: added go1.3maybe.

@rsc

This comment has been minimized.

Copy link
Contributor

commented Dec 4, 2013

Comment 6:

Labels changed: added release-none, removed go1.3maybe.

@rsc

This comment has been minimized.

Copy link
Contributor

commented Dec 4, 2013

Comment 7:

Labels changed: added repo-main.

@rsc rsc added this to the Unplanned milestone Apr 10, 2015

@bradfitz

This comment has been minimized.

Copy link
Member

commented Feb 2, 2017

/cc @broady

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants
You can’t perform that action at this time.