5 ms·
10 things you (probably) didn't know about Go (2012)
- enneff 12y agoNot sure how this got linked. The talk is not hosted there anymore (and hasn't been for some time). Here's its actual location: http://talks.golang.org/2012/10things.slide#1 http://talks.golang.org/2012/10things.slide#1
- Jake232 12y agoThe submitted link works for me.
- nealabq 12y agoIt only worked for me after 5 failures.
- guiambros 12y agoSeems it's a load balancing issue. It does load after hitting refresh multiple times.
- balls187 12y agoLink returned a 404.
- pronoiac 12y agoIt sometimes worked for me. The server's likely overwhelmed. The Coral Cache link works consistently: http://nf.wh3rd.net.nyud.net/10things/#1 http://nf.wh3rd.net.nyud.net/10things/#1
- enneff 12y agoIt's not overwhelmed. There must be a bug in my web server!
- 1_player 12y agoNested structs are really neat. I'm working on a project where I'm querying dozens of external API services, and I had to create a separate type structs for each JSON object just to get the interesting info nested in the response. I wonder why he's using a chan struct{} for the quit channel. Is there a reason for that? Is it more efficient? Usually I use a boolean for that: quit := make(chan bool) <some code> quit <- true