3 ms·
What happens when you rely on non standard behaviour of unix tools, or just non-posix tools that change from beneath you? I’m not saying that this makes powers
by dan-robertson 8y ago
What happens when you rely on non standard behaviour of unix tools, or just non-posix tools that change from beneath you?
I’m not saying that this makes powershell pipes better/worse, just that this problem isn’t unique. Microsoft tends to be reasonably committed to backwards compatibility but I don’t know the answer to the question
- Pawamoy 8y agoI think they were talking about objects at execution time, not version compatibility.
- dan-robertson 8y agoI don’t really understand what this means. The parent specifically writes “backwards compatibility.” The only other thing I think you might be referring to is if the reading process mutates the objects does that somehow affect the writing end of the pipe but I think that doesn’t make sense from a “sane way of doing inter-process communication” standpoint. Is there something else you are referring to? Could you elaborate please?