3 ms·
xonsh might be fine for interactive use, but I'd hesitate to use it for serious scripting. The nice thing about PowerShell is that it's a .Net CLR language. So,
by quanticle 10y ago
xonsh might be fine for interactive use, but I'd hesitate to use it for serious
scripting. The nice thing about PowerShell is that it's a .Net CLR language.
So, this means that anything that's accessible to .Net (including COM bindings)
is also accessible to PowerShell. This means that for example, you can script
IIS configuration and setup with PowerShell. You can script things like
importing certificates. You can stop and restart Windows services. I'd be
surprised if xonsh exposed the same amount of the Windows API as PowerShell.
- chris_wot 10y agoWith a bit of pinvoke goodness you can load unmanaged dlls also.
- BeetleB 10y agoOh, for sure. xonsh is nowhere near as powerful as PowerShell. I was pointing out that xonsh is a good shell for people who do not want to learn Powershell: people who do not need all the power. I work on Windows, but I'm not a Windows developer. I do embedded programming, and so am not familiar with most of .Net/COM. I just need to do my work on Windows, and for people coming from the UNIX world, xonsh is a shell that makes life tolerable with minimal learning necessary. Obviously, Powershell is better, but requires a lot more investment.