Pike actually says in a few places that there could be pointers when his examples use arrays. Declaring an array argument doesn't automatically get you a pointer to the contents of the array, but you can get one if it's needed. So pointers and references.
I found it even more apparent on this pass through that the language is very well built for the kind of parallel programming that I've become comfortable with in erlang. That is, go makes it very easy to spin off a new thread/process/goroutine and establish communications using channels. This is a matter of being able to easily instantiate the appropriate graph of communicating sequential processes to a computational task, receive the result of the computation when it finishes or fails, and know that all the cruft got cleaned up. So if your computation can be pipelined or fanned out onto multiple cores, That it's all statically typed and compiled and compiles fast is an appreciable advantage. I've been beating my head against the erlang dialyzer lately, which does static type analysis as an appendix to the main language involving type specifications with a syntax and predefined vocabulary that extends base erlang. That would be tolerable, but the dialyzer takes a coffee break to grovel through its computations, and I can't drink enough coffee to keep myself amused while it grovels. -- rec -- On Sat, Jul 24, 2010 at 11:17 AM, Douglas Roberts <d...@parrot-farm.net>wrote: > I thought they were good references. > > ;-] ;-] > > --Doug > > > On Sat, Jul 24, 2010 at 10:59 AM, Owen Densmore <o...@backspaces.net>wrote: > >> Thanks, good .. er .. pointers. :) >> >> -- Owen >> >> On Jul 23, 2010, at 9:16 PM, Roger Critchlow wrote: >>> >>> Oh, I see Pike gave two other talks at OSCON, no video but pdfs of the >>> slides: >>> >>> Go http://www.oscon.com/oscon2010/public/schedule/detail/15464 >>> <http://www.oscon.com/oscon2010/public/schedule/detail/15464> Another >>> Go at Language Design >>> http://www.oscon.com/oscon2010/public/schedule/detail/14760 >>> >>> On Fri, Jul 23, 2010 at 9:08 PM, Roger Critchlow <r...@elf.org> wrote: >>> >>>> Rob Pike made a presentation at the O'Reilly Open Source >>>> Conference yesterday slamming Java and C++ as part of explaining how the Go >>>> Language came about. >>>> >>>> >>>> http://infoworld.com/d/developer-world/google-executive-frustrated-java-c-complexity-375 >>>> >>>> >>>> <http://infoworld.com/d/developer-world/google-executive-frustrated-java-c-complexity-375>Ah, >>>> here's a link to a pdf for the talk and a 12:30 you tube video. >>>> >>>> http://www.oscon.com/oscon2010/public/schedule/detail/13423 >>>> >>>> <http://www.oscon.com/oscon2010/public/schedule/detail/13423>-- rec -- >>>> >>> > > ============================================================ > FRIAM Applied Complexity Group listserv > Meets Fridays 9a-11:30 at cafe at St. John's College > lectures, archives, unsubscribe, maps at http://www.friam.org >
============================================================ FRIAM Applied Complexity Group listserv Meets Fridays 9a-11:30 at cafe at St. John's College lectures, archives, unsubscribe, maps at http://www.friam.org
