I find it funny how he skips an introduction to Go saying there are many such introductions already available but explains networks and the internet in great detail!
I really like this book, but what I found most difficult when implementing a website is the authentication part.<p>How password should be encrypted? How session id should be generated and passed to the user? How session information should be saved? (cookie? file? database? memory?)<p>Also, I'd be interested in https, from theory to implementation.
Aside from being interesting and a new thing to learn, is Go used extensively in the professional world?<p>For network programming I've often used Python + Twisted + ZMQ, what are the most commonly used alternatives?
Is there any way you can control the number of native threads in go ? I wrote a small go example that used net/smtp to bombard myself with emails. Just a loop that fired off a goroutine, which each sent an email.<p>It was quite disturbing that firing off several thousand goroutines resulted in several thousand native threads - resulting the system trashing. If I inserted a very small pause between creating the go routines, this did not occur and just 1 or 2 native threads were created. I tried the runtime.GOMAXPROCS, to no awail. Is there any way of controlling this kind of behavior ?