Owner of gocasts.org here. Love that you got started before I did. I also had something very similar in mind. Want to partner up?
The commentary in the channel one is a bit off. With size 1+ it's a buffered channel and as such you could do what's shown in a single goroutine without blocking:
package main
func main() {
c := make(chan bool, 1)
c <- true
println(<-c)
}
---
†Yes, built-in functions get not only generics privilege, but overloading too. It's evidently not as pitchfork-worthy.
I like what Go offers, but is there anybody else who find code written in Go ugly?
First of all thanks for making this - I'm definitely interested in go, and resources like this really help people like me to get started writing little programs. I watched the first screencast with the http request and I had a quick question:
When doing the http request, I notice you had to check explicitly for errors in three separate places. As a guy coming from mostly a node background, I'm certainly accustomed to having to handle error checking at multiple points in async code, but usually I'll use promises to propagate the error down the chain and handle any errors that occurred at a single point. This is a really elegant way to handle errors and makes some potentially super ugly async code really clean.
Is the standard way to handle errors in async code in go what you did in this screencast, or is there a more elegant way to do it in go that you just haven't covered yet?
RSS Feed?
Some of us still use them.. incredibly useful for not having to check back all the time. Also, with a properly specified enclosure can pull down the video separately which is handy.
Or is the new trick to not have RSS and just grab email addresses? Bit of a shame if that's the case.
Enjoyed watching these so far, great to see someone stepping up to help get people started with golang.
Thanks
What editor are you using? It looks browser based. I didn't hear it mentioned in either of the screencasts I watched.
There is a typo on the home page. "Conurrency"
Cool, but I'd say Go is easy to learn. You can power through the spec, read Effective Go, figure out the go tools and GOPATH and be on your way. There's so little cruft. Go is limited in some ways, but the benefit is how simple it is.
With a language like JavaScript it can take a really long time to learn all the stupid stuff like when what this means. With Python it can also take a long time before you start having to figure out the various string representations, operator overloading and the crazy underscore variables. That kind of magical hidden complexity you see in other languages I don't think exists in Go, which makes it easy to learn.
With Go, I feel at least you can learn all that is Go in a week or so, and start building. Something like the "learn ruby/rails in 30 days" would never make sense to me given how easy it is to learn Go.
A lot of the expertise you see in Go comes from people who really know about the Go implementation. The way structs are represented in memory on different hardware, compilation optimization, the crazy stuff that most people are just not going to care about especially if they're going to run Go on some kind of cloud provider or in a vm.