3 ms·
I have tried to do the same, but i have opposite experience. I just can't grok the syntax, it always seems like a magician pulling out another "Haha! I bet you
by dgan 2y ago
I have tried to do the same, but i have opposite experience. I just can't grok the syntax, it always seems like a magician pulling out another "Haha! I bet you haven't seen this one coming !"
Like, i can't even construct the abstract model of how it's supposed to work
- plaguuuuuu 2y agoI'm even a windows .NET developer and I also find Powershell extremely weird. I'm not sure what it is.
- brazzledazzle 2y agoWould you be able to provide an example? I'm not doubting your experience, just incredibly curious since I had the opposite experience.
- dgan 2y agoSure thing : $env::Path (the semicolon? so Path is not quoted here? But when I assign a value it's quoted?) Dir -r | %($_.Name.ToLower) ( what is this? statement dreamed by utterly deranged) They took us for absolute fools
- brazzledazzle 2y agoI mean you don't need to use the convenience aliases, or use even use it exactly that way. Here's it without any aliases: Get-ChildItem -Recurse | ForEach-Object { $PSItem.Name.ToLower() } This might be a better mix of both worlds: gci -r | foreach { $PSItem.Name.ToLower() }