Also, because of the message passing and functional nature,
you don't have to worry about locking resources between the processes (threads).
Makes a whole class of issues go away (and introduces a few other ones).


On Jun 19, 2007, at 12:21 PM, Chad Woolley wrote:

Since processors will be multiplying instead of speeding up in the
future, I think erlang or something similar has got a lot of
potential.  Having the language handle multithreading for you is huge,
given how hard it is in other languages.

On 6/19/07, Thomas Hicks <[EMAIL PROTECTED]> wrote:
At 10:08 AM 6/19/2007, you wrote:
>On 6/19/07, Art Gramlich <[EMAIL PROTECTED]> wrote:
>>Erlang - You should at least work through the tutorial for it (and if >>you haven't seen it watch the video where they do live updates to the
>>system).
>
>I think you mean this:
>
>http://video.google.com/videoplay?docid=-5830318882717959520
>
>It's hilarious - like programming meets Monty Python.


Oh, my gawd!....this has got to be a deliberate joke....it couldn't be this
bad by accident....could it?

The production values are atrocious; the dialog is horrible; everyone
is speaking in slow motion, stuttering, screwing up their lines;
but, worst of all, you learn next-to-nothing about Erlang!

It's not a collision with Monty Python....it's a collision with those
"educational" filmstripes from the 50's.
         -t




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to