zlacker

[return to "The Case for Nushell (2023)"]
1. UltraS+ww[view] [source] 2026-01-07 18:14:06
>>raveni+(OP)
If you haven't tried PowerShell I strongly recommend you do. It is really well designed and the way objects are piped between commands is brilliant and very powerful. Combined with property filters you can do SQL like queries. The ConvertTo-JSON lets you export the output of any command to JSON which is amazingly useful. As an example you can dump the entire Active Directory (Assuming you have permissions) by

Get-ADObject -Filter * -Properties * | ConvertTo-JSON > ADObjects.json

And you have access to ALL of the .NET library.

◧◩
2. haolez+zz[view] [source] 2026-01-07 18:25:30
>>UltraS+ww
Until you have to quote a string that has ampersands in it :)
◧◩◪
3. ZenoAr+Me1[view] [source] 2026-01-07 21:13:22
>>haolez+zz
You mean like this...

' "Here is an ampersand... &" '

To clarify, in PowerShell there is a difference between text between single quotes (e.g. '$test') and double quotes (e.g. "$test"). Single quote strings are literal strings, so whatever text is contained within them is reproduced as written. Double quote strings are expandable strings, which means that certain text inside the string is evaluated before it is returned. If you have double quotes in a literal string, you'll see double quotes within that string, and the same should be true for ampersands.

[go to top]