Why would I use Go? Maybe because you were told to but more likely you're one of the cool kids and love awesome Gopher stickers. No shame in that game.
It's very possible you're coming into this from Ruby/Rails, PHP, or a JS background and you wanna know what all the fuss is about.
We're trying to cover all the bases and intend this documentation to be followable for a complete noob (goob?). This training will be fleshed-out haphazardly at first but will generally follow a complete beginner-to-advanced flow. The documentation certainly will be laid out in that fashion but as we complete the document we may work on some sections ahead of others. Hit us up if you want to see something done before something else. We'll rule on a first-come-first-serve basis or simply whatever we feel like doing.
Damn the man, save the empire.
You should. No one source will ever suffice. Theirs is probably better than ours.
Go to https://golang.org/ and follow the directions to set it up on your system. If the documentation isn't clear to you (I still think it relies on a bit of insider know-how) hit us up on Github and we'll look into making our own documentation.
- VimGo
- Gogland
- Whatever
Yeah so if you're coming from a web programming background this idea of workspaces, GOROOT, etc may leave in a bit of a WTFM8 moment. No worries, we'll get you there.
Check out our tutorials. We're trying to cover everything we can think of an are assuming zero knowledge of any programming or programming concepts and will cover them as in depth as we can.
Head over to the Training Section to get started. If you already know some topics, skip 'em or come back if you need clarigication.
There are also actual Go file examples that you can look at, copy, print out as napkins, whatever. They're overly-commented in order to give whoever is looking at the code for the first time as much information as possible. We may do versions that are less-commented too in case you find it annoying.