|Problems? Is your data what you think it is?|
Re^4: The problem with "The Problem with Threads"by BrowserUk (Pope)
|on Jul 20, 2014 at 13:58 UTC||Need Help??|
What are you advocating then, in regards to all this? Are you lobbying for forks and threads that don't use clone(), so you get a pure executable space, unencumbered by the parent process's ENV and filehandles? I think that would be the most desirable way to do it, but you would be forced to deal with the filehandles yourself, having to open them all manually. Most people don't expect to have to manually open stdout or stdin.
Like I said. You shouldn't throw the baby away with the bathwater.
Instead of all or nothing; how about clone-on-demand.
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.