You know, Powershell is not a bad sysadmin language at all, but certain design decision just make me go WTF. It's _really_ hard in Powershell to consume the output of a process line by line. That stuff is trivial in bash. (For the curious, I'm setting up end-to-end tests and for that I need to start a few servers and wait for them to be ready. The servers conveniently announce that in a line on stdout. Due to Powershell not extending the whole stream metaphor to process output however I think it'll be easier for me to rig the servers to create a file / send a message to the supervisor script.)