|
|
|
|
|
by riperoni
770 days ago
|
|
Either i overread it or one major quirk is totally not touched on: PowerShell is case-insensitive in as many places as possible, except file paths or the likes. You can actually call .NET methods with completely nuts casing: "asdfg".tOupPer() works. Also variable names with only different cases resolve the same, i.e. $var is the same variable as $Var. String comparison with PowerShell operators is case-insensitive and it has special operators to match case sensitivity. RegEx operators behave the same way. Using the .NET methods however conserves case-sensitivity. I enjoy using PowerShell a lot. In many of places for scripting processes (Windows server adminisitration) it has an easier entry point than Python. And handling complex objects is kind of trivial. The Windows PowerShell really shows its age by now though and I hope the new PowerShell will be included by default, too. |
|