News for hackers. Stuff that matters.
Re:EventMachine: scalable non-blocking i/o in ruby by axod on Monday March 15, 2010 @05:59PM (#1194258)
Sure, you don't know the exact order your code executes if it has external inputs :) but you know that your code will execute 'linearly' and then adhere to any program flow constructs you put in, and nothing else.

You can be 100% sure that it won't suddenly stop executing here, and jump over to some totally disconnected bit of code for a while, then jump back.

You don't have to worry about a whole class of bugs which take up weeks/months of peoples time.

Not sure what you mean @ timers, I was really talking about async/event driven in general. Timers seem like an implementation specific detail on top of that. I haven't really seen any issues myself there :/

Re:EventMachine: scalable non-blocking i/o in ruby by jerf on Monday March 15, 2010 @10:31PM (#1194765)
"You don't have to worry about a whole class of bugs which take up weeks/months of peoples time."

I reiterate, you need to spend some quality time with Erlang. This time I recommend http://erlang.org/download/erlang-book-part1.pdf ; Erlang has some powerful answers to those "whole class of bugs".

(Actually, not being aware of that does rather make sense of the rest of your views. I have first-hand experience that Erlang really does make those problems go away; I like to say that Erlang takes concurrent programming from an exponential problem to a polynomial one. It still isn't "trivial" and I don't know that it ever can be, but it makes it so a human can do it.)