2 ms·
> aliases, etc. Aliases only hide verbosity in base commands. If the parameters and switches are overly verbose too, they can't help you there. > dotNet I'm
by franga2000 6y ago
> aliases, etc.
Aliases only hide verbosity in base commands. If the parameters and switches are overly verbose too, they can't help you there.
> dotNet
I'm not saying it's not good and certainly not just because it's from Microsoft. I've done Windows and Linux development and while it's the way to go on Windows, I've never missed it on Linux.
> You cant really compare PowerShell with mainstream langauges
I never intended to, but you called it as powerful as it gets, which really isn't true. I was just giving you examples of why it isn't.
> reinventing the universe
See, to me, the reason I can't switch to powershell is because it seems to reinvent too much - both from a shell and a scripting perspective.
> Python
The whole reason why I brought it up was to continue my original point of "unimpressive for scripting". While I appreciate the convenience of using the same language for shell and scripting, I have no problem using a non-shell language to do more complex things.
Either way, you have successfully convinced me to give Powershell a try one more time once I get some free time to experiment.
- majkinetor 6y ago> If the parameters and switches are overly verbose too, they can't help you there. There are parameter aliases too, proxy vars and you can shorten their name to unique subset which gets you as far as you can get anywhere > Either way, you have successfully convinced me to give Powershell a try one more time once I get some free time to experiment. Thats good to know :) Do it right, and you wont regret it, I can promise that.