The file-oriented design of UNIX leads to such completely asinine misfeatures as the inability to have shared memory clean itself up as soon as the last process using it terminates.
-
-
-
This is completely untrue. Just unlink it as soon as you create it and pass the fd around.
-
OK, but then how do you clean up the UNIX-domain socket used for FD passing? Exact same problem.
-
If it's sharing among related processes, you just inherit the fd. No need to pass over socket. If client-server, server owns listening socket name.
-
Whenever you have named/addressable resources someone has to be responsible for ownership & lifetime of name.
-
UNIX needs a flag to open, bind and shm_open that says, delete link if the last handle that was opened through that link is closed.
-
TCP sockets work this way, so why can't UNIX optionally also?
-
This has inherent race condition flaws.
- 5 more replies
New conversation -
-
-
I've no opinion on this, but... One of the biggest complaints I've heard re: POSIX tools vs Powershell is that POSIX-detractors think text isn't structured enough to pass between programs, and we jump thru hoops to make it structured enough for sh pipes to work.
-
A lot of sloppy scripts handle text sloppily. A lot of API-based scripts/programs handle their APIs sloppily. I don't think text is the issue here.
-
The issues are documented data formats suitable for interchange, ability to use them with diverse tools and tools that haven't even been written or imagined yet, ability to use data without invoking code, ...
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.