I generally like the style of this and "Learn You a Haskell..." which it is styled after. I was thinking of using the style for Python, Perl, or Tcl version.
Being already familiar with Erlang, I wish I had this resource while starting out. This is way easier to read for starting out from scratch on Erlang, and is definitely a light but comprehensive read.
I found myself enjoying this, even though all of these bad grammar titled randomly weird artwork _why-inspired programming books are surely a cliché now.
By the way, if you are a fan of a language trying to replace Erlang (with my blessing), OTP is your real target. The shared-nothing processes and message passing and all that stuff is really all there with the goal of making the OTP libraries possible. Copy all that other stuff but miss the OTP functionality, and you will have copied the style while missing the substance.
Agreed that OTP is the meat. After writing my first gen_server, Erlang finally clicked with me. This series of blog posts served as a great tutorial to all the OTP behaviours: http://spawnlink.com/articles/tag/otp-introduction/
Prolog's syntax is a lot cleaner, though - if you took your favorite language and added lots of new operators, so they were clearly the new language, how would it turn out? A lot of minor issues with Erlang (e.g. the whole ; vs , vs . thing) come from that.
Once you get past the surface details, though, Erlang kicks ass. Hold on!
13 comments
[ 2.8 ms ] story [ 28.6 ms ] threadIt's nicely written and light enough as well, nothing too heavy.
Prolog's syntax is a lot cleaner, though - if you took your favorite language and added lots of new operators, so they were clearly the new language, how would it turn out? A lot of minor issues with Erlang (e.g. the whole ; vs , vs . thing) come from that.
Once you get past the surface details, though, Erlang kicks ass. Hold on!
(Prolog is awesome, too.)