From: Tony Arcieri <tony.arcieri@...>
Date: 2012-07-06T02:38:46+09:00
Subject: Re: Green threads in 1.9.* ?

--00151761c7aa7cbe9d04c4189efe
Content-Type: text/plain; charset=ISO-8859-1

On Thu, Jul 5, 2012 at 10:26 AM, rex goxman <lists@ruby-forum.com> wrote:

> 1.  Tell that to Erlangers.
>

I assure you, I am quite familiar with Erlang:
https://github.com/tarcieri/reia

Whenever an OTP process (e.g. gen_server, gen_event) crashes, the reason
for the crash is meticulously logged by the OTP logging framework. This is
pretty much the only way to debug asynchronous behaviors, as if the
exceptions are swallowed by default you have no outward indication of what
happened.

Erlang provides a great example of a system that is the exact opposite of
the one you are proposing.

-- 
Tony Arcieri

--00151761c7aa7cbe9d04c4189efe
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div class=3D"gmail_quote">On Thu, Jul 5, 2012 at 10:26 AM, rex goxman <spa=
n dir=3D"ltr">&lt;<a href=3D"mailto:lists@ruby-forum.com" target=3D"_blank"=
>lists@ruby-forum.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_q=
uote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1e=
x">

<div class=3D"im">1. =A0Tell that to Erlangers.</div></blockquote><div><br>=
</div><div>I assure you, I am quite familiar with Erlang: <a href=3D"https:=
//github.com/tarcieri/reia">https://github.com/tarcieri/reia</a></div><div>=
<br>

</div><div>Whenever an OTP process (e.g. gen_server, gen_event) crashes, th=
e reason for the crash is meticulously logged by the OTP logging framework.=
 This is pretty much the only way to debug asynchronous behaviors, as if th=
e exceptions are swallowed by default you have no outward indication of wha=
t happened.</div>

<div><br></div><div>Erlang provides a great example of a system that is the=
 exact opposite of the one you are proposing.</div><div><br></div></div>-- =
<br>Tony Arcieri<br><br>

--00151761c7aa7cbe9d04c4189efe--