News for hackers. Stuff that matters.
Re:Concurrency in Go (or, Erlang done right) by metabrew on Thursday December 22, 2011 @03:11PM (#3383055)
I like go and erlang, but the title is a troll.. Nowhere in the presentation does it compare the pros and cons of the go approach to how erlang does things.

Sometimes selective receive with erlang's pattern matching is really useful. How about erlang's supervision hierarchies and recovering from errors? Erlang's hot code upgrades on long-running systems to avoid any downtime?

Since go has/needs mutexes, it's laughable to say it's "erlang done right". It's nothing like erlang in that sense.

Re:Concurrency in Go (or, Erlang done right) by mdwrigh2 on Thursday December 22, 2011 @04:23PM (#3383333)
I agree the title is misleading (I should also point out that this isn't my slide deck, but one done by Dmitry Vyukov).

> Since go has/needs mutexes

I'm not sure it's really fair to say Go needs mutexes, just that they are available for you if you need the performance.

Re:Concurrency in Go (or, Erlang done right) by jlouis on Thursday December 22, 2011 @04:27PM (#3383347)
One funny thing is that the counting example has a really simple and very fast solution in Erlang. Shove the counter into an ETS table and use ets:update_counter as the call to manipulate it.