In the 1970's the then current and accepted theory by the high priests was that pollution (i.e industrial waste gases) was going to freeze the Earth. Now it is going to burn it.
For someone who claims to be skeptical and demanding of evidence before accepting something as true... why does that go away when you start making claims? You make a mockery of yourself when you claim that there was a accepted theory in the 70's about global freezing. There was no such thing.
There were some articles in Newsweek and similar magazines that made that sort of claim... but they didn't reference any conclusive peer reviewed work.
In short, you're more then happy to make claims without a shred of evidence. Instead of expecting us to show you the data and experiments, if you want to get to the bottom of it... you need to go read, learn, and understand what's already out there. Scientists have done the work; the onus is on you to understand it before you dismiss it.
Well in the application we are talking about there isn't any need for two-way communication.
What? The application we're talking about is X11, and the X11 protocol requires two-way communication. At the very least you have to be able to receive status reports back (success/failure), and there are all those event notifications (key press, mouse movement, etc.) to consider.
Besides, if you look at Stevens' example you'll see only N+1 one-way pipes are required, not 2N pipes (where N is the number of clients).
The contents of that book do not appear to be available online (and I'm not buying it just for this discussion), but from the source-code examples I assume you're referring to the fact that you can use just one pipe for all communication to the server, and separate pipes for communication to the clients. That works, but the server has no way of knowing which client sent a given message (aside from implementing some sort of ad-hoc message signing protocol itself), whereas sockets given each client a secure path to the server so that a misbehaving or malicious client can't send messages on some other client's behalf. Given that creating a socket takes about the same amount of effort as creating a FIFO, I don't see any reason to waste time mimicking sockets with FIFO pairs (even if half the pair is common to all clients).
Interestingly enough Stevens doesn't consider sockets to be an IPC mechanism.
"Oops". That's a fairly embarrassing omission for a book with Unix, network programming, and IPC all right there in the title.
Pumping the breaks used to work, it doesn't anymore.
See, that's only true in cars with ABS, and they don't all have it.
The only time pumping the brakes even repeatedly will harm you is when you're experiencing a runaway condition and your engine is at WOT, because it is probably not producing enough vacuum to operate them at their full potential. In most vehicles, though, the vacuum storage tank provides enough for a couple decent depressions... and in any case, you don't need that much travel. My vehicles both produce vacuum with a vacuum pump because they are turbocharged diesels, so they will produce more of it at full RPM... so I don't personally have to care about that, and can use my brakes as necessary. The Mercedes does not have any ABS, and the Ford only has it in the rear.
I don't have quite as much of a problem with my local/state taxes going for schools. I kind of consider them to be part of 'infrastructure', much like a police stations and a firehouse.
I have several big problems with my tax dollars going to federally unfunded-mandated, state-specified indoctrination stations. I remember clearly what it was like to go to school in my state, and consider it institutionalized child abuse.
Real Users are afraid they'll break the machine -- but they're never afraid to break your face.