| Follow @yevthedev
Software Engineer, with an open source governance bend. Occasional developer outreacher. All opinions are my own.
Brain droppings here.
Software Engineer, with an open source governance bend. Occasional developer outreacher. All opinions are my own.
Brain droppings here.
Authored Comments
PowerShell does include the “dir” cmdlet (alias for Get-ChildItem) which serves the purpose of “ls”. The original Windows version of PowerShell actually aliased it as “ls” as well. I’m assuming that alias was removed so as to not conflict with the native “ls” command on Posix platforms.
You can read about how Get-ChildItem (aka “dir”) works with files here: https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell…
And with PowerShell you don’t need as many parameters to specify what information to return, because what you get are .Net objects whose properties you can query with Where-Object (aka “where”, aka “?”) cmdlet.
Do not assume a solution does not exist where it is not immediately apparent.
I haven't encountered the inconsistency you're describing. Can you give some examples?