4 ms·
> DSCv3 doesn't depend on PowerShell. You can use DSCv3 without PowerShell installed So what's the point of PowerShell if most new CLI tools from Microsoft are
by debugnik 2y ago
> DSCv3 doesn't depend on PowerShell. You can use DSCv3 without PowerShell installed
So what's the point of PowerShell if most new CLI tools from Microsoft aren't PS modules and can't take advantage of the .NET object model, even on Windows (see also winget)? Why is DSCv3 under the powershell organisation if it's just a regular Rust CLI?
- bradhe 2y agoSeems like classic Microsoft to me.
- 7bit 2y agoDSCv3 is compatible to v2, except with MOF files, in my understanding. You can continue to use PowerShell with it. I can only speculate, but since there is no more LCM, a binary was needed to properly run DSCv3 on your machine.
- 7bit 2y agoDSCv3 is compatible to v2, except with MOF files, in my understanding. You can continue to use PowerShell with it. I can only speculate, but since there is no more LCM, a binary was needed to properly run DSCv3 on your machine.
- debugnik 2y agoI see now that not all the PS files are for tests, there's one adapter PS module for compatibility. But that's still damning: If Microsoft themselves are building their PS modules as ConvertTo/From-Json wrappers for native CLIs (or being shipped at all, like winget's PS module), instead of shipping C# cmdlets and a domain model for .NET, then PowerShell is superfluous and we should be dropping it, even on Windows, for a JSON-aware shell or a more common shell with tools like jq.