News for hackers. Stuff that matters.
Re:First thoughts on Erlang by al3x on Saturday January 15, 2011 @05:51PM (#2108040)
This quote from the post says it all: "I actually haven’t finished the book yet – I’m at the end of the first chapter".

It's great that the author is learning a new language, but maybe wait until you've actually done something with it or at least finished the book to write about it? First impressions don't mean much.

Re:First thoughts on Erlang by reiddraper on Saturday January 15, 2011 @08:41PM (#2108348)
Actually, that's not what he said. Here's the full quote: "I’m at the end of the first chapter that explains how Erlang’s concurrency features work"

A quick look shows that it's the sixth chapter. Either way, he's clear about this disclaimer, and his post was enough to peak my interest in this specific book.

For you, first impressions _do_ seem to mean much.

Re:First thoughts on Erlang by chops on Sunday January 16, 2011 @12:03AM (#2108718)
That was also the first chapter in the book where suddenly Erlang seemed freaking amazing. Up until then, it was just a functional language with an odd syntax. After the introduction to message passing and concurrency, I was in love.
Re:First thoughts on Erlang by Qz on Saturday January 15, 2011 @08:46PM (#2108353)
It's called "First thoughts on Erlang" for a reason.
Re:First thoughts on Erlang by silentbicycle on Saturday January 15, 2011 @07:19PM (#2108200)
Indeed. If anything, the programming landscape already has way too many inaccurate first impressions getting in the way of real discussion.