News for hackers. Stuff that matters.
Re:Introducing nushell by vthriller on Friday August 23, 2019 @09:14PM (#20784493)
> You just get all the data, and filter what you want programaticly.

There are definitely cases when you're better off with producer-side filtering. For example, `find` allows you to not traverse certain directories with -prune, which might save a lot of resources.

Re:Introducing nushell by jodrellblank on Saturday August 24, 2019 @12:05AM (#20785151)
PowerShell has a lot of "corrections" of this kind, to get producer-side filtering. e.g. Getting all Windows Eventlogs, then filtering client side turned out to be quite bad, so Get-EventLog became Get-WinEvent with a lot more filtering controls.

Cmdlets which get data, like Get-AdUser or Get-MessageTrackingLog in Exchange, or Get-CimInstance often have a lot of common filtering parameters as well as a more general -Filter or -Query "build your own".

Big source of annoyance where you can't do that, but might want to.

Re:Introducing nushell by felixfbecker on Saturday August 24, 2019 @05:00AM (#20786082)
It also generally applies to concept of wildcards/globs not just to file paths, but many parameters. So a cmdlet like Get-User with a -Name parameter to get a user with a certain name can also be called with John* to get all users with first name John. In my experience the filtering options are pretty consistent