>>51061275I work with it daily doing regular helpdesk and sysadmining.
It's a glorious tool if you know some OOP in advance.
> or command promptUse it if you must, but if you're after a job, Powershell will impress an employer much more than batch scripting. One, everyone fucking knows batch, the language has remained unchanged for decades and the toolset is nonexistant. It's really just a dumb shell you plug inconsistent programs into, with inconsistent syntax. Two, fucking remote script execution.
Does your commandlet support the -ComputerName arg? Cool, you can call a variable or (Get-Content C:\...) and execute the command in parallel on all those machines. If not, you can do the same thing with Invoke-Command.
One thing I'll give Powershell is that it's flexible compared to batch.
(remember, we never compare a Windows shell to a UNIX shell, they cannot manage each other and are incomparible)
>>51061445You're not a Windows admin, that's your problem.
Powershell was made because Interix/SUA/SFU couldn't do shit with Windows: It's all APIs. Linux is all text documents - it's an incompatible management model.
>>51061798I guess the verbose nature of Powershell makes stuff a bit more.. long to write. I guess some find it helpful, others a burden.
wget isn't that great of an example, just pointing it out. wget -> Invoke-WebRequest in Powershell.
I like the verbosity, but I understand if you don't. UNIX and Stallman never wasted any characters when naming the utils used today, so having to get used to tabcompletion instead of just really short, ambiguous (not nessecarily a bad thing) util names.
