A Pythonista's Impressions of Erlang

I am planning to write a poker server in Erlang. Why? A couple of reasons. First off, I have heard that the concurrency support in it is excellent. Secondly, A quick glance gave me the impression that it was, at least, not brain-dead. Third, it's been a long time since I learned a new language, so I'm planning to do it for kicks.

As such, for the last few days, I've been playing around with the language, and I have begun to form my opinions on it. Since I've been pretty busy, I haven't had too much time to play with it, and as such my opinions are half-baked. Since that never stopped me from writing before, here they are.

If I'm wrong somewhere (and I'm sure I am) drop me a comment, and I'll fix it.

The Good

The Not-Sure-If-It's-Good-Or-Not

The Bad

Well, that's it for now. I'm sure I left some stuff out, and I'm sure you disagree with some of what I've said, so leave me a comment with what you think or drop me an email.

Overall, I think Erlang has some neat features - especially pattern matching and guards. Furthermore, if what everyone says is true, its concurrency is fast and well-designed. Although the lack of proper documentation is a turn-off, I feel like I'll be able to learn what I need to know from reading the very readily available code. I'm still going to give it a shot, which is a good sign.

Jan 10, 2005