|Problems? Is your data what you think it is?|
Re^5: perl5 road map?by BrowserUk (Pope)
|on Mar 24, 2012 at 23:01 UTC||Need Help??|
Erlang processes don't share anything, hence they actually different from 'green threads'
Of course they share stuff. It is an illusion of the programing model -- functional programming with single assignment variables -- that they appear not to. But just as they don't throw away a chunk of ram just because you used it once, there is nothing to stop errant (compiler or runtime) code scribbling all over everything in the process virtual memory space.
Everything lives in a single process; ergo, everything is shared.
So why the hell you first gave useless demonstration in Perl,
Because the OP said: "who determine if ... perl5? For example: can create 1000+ fast,light, reliable threads easily without any crash like erlang"
I simply demonstrated that it was possible to do that now, and had been possible for a long time.
But I went on to say: "Of course, I cannot actually think of a valid use for it, but doing it is not a problem."
My exact point was that it is just as useless to do in Perl as it is in Erlang or Go -- but if you want to, you can.
With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
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.