You claim that forks duplicate everything? I think not. At least not on any OS which implements copy on write memory, which would be any semi-current *nix. And in many applications it is OK if communication overhead is slightly more in order to benefit from the saved memory and increased protection.
As for the rest, I haven't tracked to see if people's experience with Perl's threading in the last half year is as bad as it had been before that. It probably has improved, though not to the point where I'd be willing to put it into production. But my general comments about threading remain true, and my specific comments about Perl's thread model in specific are, to the best of my knowledge, accurate. If you have specific examples to change my mind, that would be one thing. But you don't appear to, instead you're just telling me that what I've said is red herrings and wrong, without providing me with any specifics.
Since I feel no need to convince you of anything, and I don't feel that this conversation is going anywhere I'm exiting the conversation here.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
