It's a big file for relatively few slides, but they're certainly tantilising aren't they? I don't suppose that you came across any more details of the talks content did you? I followed all the obvious looking links, but didn't find anything that put any flesh on the bones of the slides. I'd love to hear the talk, but that ain't gonna happen any time soon.

There is an aweful lot to like about Erlang. One thing that I think contributes to it's effectiveness and useability is that it was developed and evolved by non-academics to solve real-world problems with real world, commercial, time and money constraints. As such, it avoids many of the theoretical and 'purity' imperatives that litter academically devloped languages.

This is especially true with the absence of gargon and notation in the documentation. It's very refreshing to see the purpose and feature sets of an FP language described in terms of the real world problems that they evolved to solved; rather than having the real world treated as a dirty black box that the pure world of FP can encapsulate and control.

As an aside. It's nice to see that others think like me about that "Computers are state machines; threads are for people who can't do state machines" quote ;) I've tried before to think of an appropriate analogy for that non sequitur and I finally came up with one:

Cooking is Chemistry; and people without Chemistry degrees shouldn't be allowed to cook.

Anyone who's seen Heston Blumenthal's TV series will understand that whilst the first clause of that statement is very true, if the second were, mass starvation would not be confined to war and drought ridden areas of the Third World.


Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
"Too many [] have been sedated by an oppressive environment of political correctness and risk aversion."

In reply to Re^4: The State of Parallel Computing in perl 2007? by BrowserUk
in thread The State of Parallel Computing in perl 2007? by jettero

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.