Re: Are We Back to the "Wars" Now ?

On 11/19/2024 19:23, Lawrence D'Oliveiro wrote:

On Mon, 18 Nov 2024 09:45:07 -0500, Phillip Frabott wrote:
 

I think the point that is being made by calling pipes a "temp files" is
that they are not persistent.

 Named pipes can indeed be persistent.

Sure, but then your just creating a file with all the limitations that come from that. IPC only benefits you when you use unnamed or traditional pipes (performance and resources). Also, the pipe still requires something on the other side of the transaction which might not exist at some later point. Whereas a file on hard storage will almost always be able to be transacted (assuming permissions of course) regardless of what processes are (or are not) available. Also pipes also require realtime processing, whereas storing things in a file can provide for delayed/deferred processing at a later time.
Now, sure piping a command may be less typing, but there is no real tangible benefit from the technical side from using a pipe vs typing the command out over multiple lines of commands, the transaction remains the same in both cases. But having non-persistent pipes gives you speed and performance perks (and in most cases uses less RAM). So if your going to do named pipes just know you aren't getting the real benefits of the IPC if it's just going to write a file anyways.
--
Phillip Frabott
----------
- Adam: Is a void really a void if it returns?
- Jack: No, it's just nullspace at that point.
----------