3 ms·
xonsh looks interesting. My first question would be along the lines of "do you get command completion and nice syntax highlighting in the shell?" but I see in y
by YeGoblynQueenne 10y ago
xonsh looks interesting. My first question would be along the lines of "do you get command completion and nice syntax highlighting in the shell?" but I see in your link that it does have those, so that's a great start.
My other worry is that there's going to be some things it's hard to do _on windows_ for any shell that isn't created by microsoft. Which is not the fault of xonsh, or any other alternative shell, obviously- but which might make psh a better deal in some cases.
Can't think of an example though, to be honest :)
- quanticle 10y agoxonsh 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.