Improve the & background operator (consistency with bash, richer functionality)

[KirkMunro]

No description provided.

[dragonwolf83]

Ok, so my comments are in reverse order, lol. First time clicking "Review". Makes more sense if you read the last comment first.

[joeyaiello]

Trying to do more async reviews outside of Committee meetings, so that means my review here is not binding by any means. Just giving my (often naive) take.

Right now, I'm okay with $! and the new ProcessId property, but I have concerns about console overlays, as well as the change to --% (which I don't believe can be easily implemented, though I'd love to be proven wrong). I think we should document workarounds (inline in my comments) around the --% scenario.

[KirkMunro]

Trying to do more async reviews outside of Committee meetings, so that means my review here is not binding by any means. Just giving my (often naive) take.

This is very much appreciated. Even just a non-binding "gut" take from you guys on these is very helpful, so I thank you for that.

[joeyaiello]

After some discussion, @PowerShell/powershell-committee feels that most of this proposal is not useful and/or straightforward enough to accept:

• Muxing output streams from multiple jobs in an async interactive session sounds confusing to end users, and if it's just a simple tail you want, that can be accomplished with Receive-Job -Wait
• We don't believe that $! has enough utility to be an automatic variable. You can already do things like $foo = 1..3 | % {start-job {$_}}

We did, however, agree that a ProcessId property would immensely useful to folks, and should probably be added to PSRemotingJob, but that can be handled purely in an issue.

At a high-level, we think there's some improvements we could make to the UX of the entire job system (especially using ThreadJobs), but it's not currently a priority for us.