Since people are curious Ill explain why:
I need to build our project from the remote repo using a PowerShell script (.ps1). I’m using Bash in the VSCode terminal, I have to run the .ps1 script in a new Command Prompt because the compilation takes around 5 minutes and I need my terminal for other things. To do this, the only way is to run a batch file that executes the .ps1 script.
Its an automation so I dont need to touch powershell whatsover and remain in bash terminal. Instead of opening several windows, I automated all so it only takes 1 alias to compile my shit.
The compilation also requires several inputs and “Key Presses”, so I automated all of that in the Batch file.
You’re missing nushell. Its the same idea as power shell, but written in rust and with better commandlet naming schemes.
Powershell is good, but it has that Microsoft funk on it. You can tell none of the people who develop it use it much. Warts everywhere.
Thanks for the reference. I’m looking at it and I think you’re right.
OMG the naming schemes for powershell is enough for me to stay away. A +20char name for a command that shares the first 10 chars with 15 other commands, so you can’t just tab through it? No thanks!
Will look into nushell though, thanks for the advice.
nutshell is very cool, and I think the “structured data for everything” that powershell has is a good idea, but the implementation is meh.
Nushell gives you that structure and you can mix I’m your favorite Unix utils because its still just a Unix shell at the end of the day. Its nice. If you’ve written some scripts with powershell, nutshell will feel very similar, but with moar freedom and less stupid names.