In our last disagreement you would not even so much as recognize my arguments about context, just completely ignoring anything I said. And there you were taking one phrase out of its qualifying context. Here I am making an objection to a complete thought that was part of your reply to the OP; yes, not one pertinent to your main point.
Why am I doing so? Because you seem to have elected yourself defender of ithreads to the point where you attack even true and reasonable cautionary points about them with a variety of shenanigans designed more to conceal than expose truth. The truth is that ithreads are a very different beast than people coming from other languages may expect. They are slow to start and tend to cause memory bloat. Anywhere there is support for copy-on-write fork, fork and some variety of IPC is almost always a better choice.
If that's politics, so be it. Don't bother responding, I'm not going to read it.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
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:
Outside of code tags, you may need to use entities for some characters:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||