I keep hearing this regularly: powershell is often a problem for corporate users of clojure on Windows. I'm posting this here as feedback. https://github.com/babashka/babashka.process/issues/15#issuecomment-687035007
Unfortunately that does not give enough to do anything. If Powershell is so much restricted, than WSL is likely not an option too, because installation images put on such corporate boxes is already outdated and flawed.
Yes.
But the deps.exe approach does work for these users
Yes. It's a great option.
I mean, it has been suggested before to get rid of PowerShell for the official Clojure tool, because it's sometimes painful
It's less of the problem than we think. Windows 10 is based around PSH and it's not going away. And these companies they eventually gonna need to do the right thing.
It's still pretty annoying. If I do a GraalVM build on Windows, I need to do this from cmd.exe (because of a .bat file in Visual Studio that sets the right env vars) and I have to jump through some hoops with clojure (if I didn't have deps.exe)
Not a major problem for me personally, because I know how to work around it, but I keep hearing these reports from time to time