Actually, the privatization of the military has already started. The military already doesn't cook their own meals: Haliburton does that. And let's not even bring up Blackwater...
Slashdot videos: Now with more Slashdot!
We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).
Tosh.0 reviewed the Ipad. Here's the link:
I still don't understand that argument.
The post office is amazing!
I can take a physical piece of paper, put it in a mailbox and someone will pick it up and send it to my desired location in a matter of a day to a few days. All for a few measly cents. How is that inefficient?
That's partially true.
I also lived and worked in Manhattan during 9/11.
There was a cellphone tower on top of one of the two towers which killed cellphones for the lower region of the island, but cellphones were working just fine as low as 35th st. I called my parents back home from my apartment on 91st street and spoke with a co-worker who was already at work and watching the events unfold from the corner of 35th and 7th.
You are definitely correct about cellphones not working down in the financial district however.
I'm not trolling here, I'm genuinely curious...
What makes using multiple processes in an app better than threading?
I've used both in programming and a nutshell breakdown that I understand and that I've experienced is thus:
* Threading is quick and can "share" memory and resources but requires the programmer to synchronize access to shared resources through mutexes and such
* Processes have no such synchronization problem and *can* share memory but it's much more difficult to do so, instead making use of inter-process communication via pipes and unix sockets, which in my experience is much more time consuming and difficult than sharing memory via threads but still easier than sharing memory between processes.
Again, this is a nutshell and oversimplified comparison, but from where I stand, I've always thought threading was easier and quicker to use and works just as well, if not better, than multi-process apps. Of course there are times when it's more appropriate to use processes rather than threads.
Again, what's your take on the matter?