Comments on: Programming Erlang http://kconrails.com/2009/03/23/programming-erlang/         Adventures of Jaime Bellmyer, A Freelance Ruby on Rails Developer in Kansas City Wed, 19 Oct 2011 02:07:23 +0000 hourly 1 http://wordpress.com/ By: jbellmyer http://kconrails.com/2009/03/23/programming-erlang/#comment-27 Fri, 04 Dec 2009 01:34:11 +0000 http://kconrails.wordpress.com/?p=4#comment-27 I agree, different tools for different jobs. However, I’m addressing the recent buzz surrounding Erlang in the Ruby community. It’s an old debate, speed of execution vs. speed of development.

I believe most of the time, development speed is more important than execution time because cpu cycles are always getting cheaper. Development costs tend to trend the opposite.

In the end, it’s all about cost. If something is cpu-intensive enough to warrant concurrency, then sacrificing rapid development is probably worth it.

]]> By: B http://kconrails.com/2009/03/23/programming-erlang/#comment-20 Thu, 24 Sep 2009 16:36:15 +0000 http://kconrails.wordpress.com/?p=4#comment-20 ” {_,{_,{_,Name},_},_} = Person ”
Assuming you have defined a record ‘person’, you can do something like :
Name = Person#person.name

“Does it solve one problem (concurrency), only to sacrifice good things like OOP?”
Erlang is not designed to be object orientated, just like any language it is only one tool for the job and has its own pitfalls. No OOP is not a sacrifice, it was a design choice (OOP is not the One And Only solution.)

]]>