When I develop on windows I use Powershell. I haven’t looked into WSL due to laziness, but powershell works 99% of the time for what I need.
Powershell is essentially the “mainstay” for windows. If you wanted to be a system admin, it can be your best friend. Doing something like WSL could work, but you also might end up fighting the interop more than actually doing something.
Alternatives like git-bash, cmd aren’t as mainstream and you end up with a similar problem as WSL, where it might stop working if your doing something different. Powershell can have this same problem, especially if you start trying to do
bash stuff, but there are more resources to work around such scenarios.
There are multiple ways to “automate stuff” in VSCode, but I don’t believe powershell is one of the top options unless you want to get vendor locked into powershell. If your doing a web-dev project, the most you’d use powershell is to call
This doesn’t mean you can’t learn to use Powershell, but you probably would use it to automate stuff within Windows itself.
For example, I remember I was given a project to move around around 20k images. I had to restructure the images based on their name and size into a new folder structure and rename them following a new format. Obviously a single human working on this manually would take a while, so the only option was to automate it.
It took about a day and a half to learn and write up the script to get the meta-data, and test it with a few hundred files. Worked pretty much flawlessly after only a day and a half of work, and the person who gave me the project was very happy.