Disclaimer: I'm a PM who works on PowerShell at Microsoft
There's a bunch of 3rd-party modules out there that do a great job of offering parallelism[1][2][3], and we also support the notion of "PowerShell Jobs"[4] (which one or two of those third-party implementations actually build on to achieve what they're doing).
However, we decided that strong parallelism support is important enough to build into the language, so we're mulling on a first-party design.
If you're interested, we've got an RFC out where we're looking for feedback on the parallelism/concurrency design.[5]
There's a bunch of 3rd-party modules out there that do a great job of offering parallelism[1][2][3], and we also support the notion of "PowerShell Jobs"[4] (which one or two of those third-party implementations actually build on to achieve what they're doing).
However, we decided that strong parallelism support is important enough to build into the language, so we're mulling on a first-party design.
If you're interested, we've got an RFC out where we're looking for feedback on the parallelism/concurrency design.[5]
[1]: https://www.powershellgallery.com/packages/PSParallel/
[2]: https://www.powershellgallery.com/packages/SplitPipeline
[3]: https://github.com/RamblingCookieMonster/Invoke-Parallel
[4]: https://msdn.microsoft.com/en-us/powershell/reference/5.1/mi...
[5]: https://github.com/PowerShell/PowerShell-RFC/issues/85