On Tue, May 7, 2013 at 11:36 PM, Levi Pearson <[email protected]> wrote:
> And to take another little digression down history lane, Go's > concurrency features such as goroutines are ultimately derived from > early work on specifying/formally describing concurrent processes, > namely the model of Communicating Sequential Processes as first > described in a paper by C.A.R Hoare. He later published a book > describing the system, which is now available for free here: > http://www.usingcsp.com/cspbook.pdf > > +1 for this paper. If you only read one technical paper in your lifetime, I'd recommend this one. The original paper is here: http://dl.acm.org/citation.cfm?doid=359576.359585. It requires an ACM subscription. I tried to find a free one, but haven't as of yet. I like the book and it's a lot easier to read, but it doesn't have the same wow factor I got when I first understood what he was talking about in the original article. > Anyway, goroutines are a significant thing but not the only nice > feature of Go. For one thing, they finally ditched C's terrible type > declaration syntax! That's reason enough to switch to it right there. > > I was surprised at the level of interest in Go at OpenWest. It was meant to be only 1/3 of my presentation, but it was pretty clear from the beginning that it was pretty much the only reason some people came. I'm thinking next year I'll plan on doing a presentation solely on Go. Pike has been very open about how Go came about and what it is trying solve. Here is one: http://www.infoq.com/presentations/Go-Google. Here is a written version: http://talks.golang.org/2012/splash.article. /* PLUG: http://plug.org, #utah on irc.freenode.net Unsubscribe: http://plug.org/mailman/options/plug Don't fear the penguin. */
