nushell VS PowerShell

Most of the time I'm in Powershell which, thanks to Powershell Core, is now cross-platform and incredibly powerful. But I'm finding myself also using Nu more and more. In both shells I also use the Databricks CLI a lot. Want to check the status of jobs? Use the CLI. Want to upload and download data? Use the CLI. And so on.

There are also some new shells in the list, including Tabbyand Nushell, which both had around 7K stars, though Nushell is a much newer project

I'd recommend to take a look at https://www.nushell.sh/ which has structured output, but displays it neatly when printing to the terminal.

I'm surprised to see no mention of nushell [0] I've tried it a while ago and seemed really promising

[0] https://www.nushell.sh/

Has anyone tried out Nushell recently? I've been playing with it for the last few days, and it's shaping up into something pretty impressive for data/pipeline handling.

But no, people should use pipes in Nushell, of course! ;-P

Might want to add something about why someone would want this over something like say NuShell. Only thing I'm seeing right now seems to be the Lua thing.. which is kind of irrelevant to me anyway. Thanks.

You might find this interesting

There's also Nushell, which I've never used, which is similar to Powershell in that commands return structured data rather than text, but I believe has a more functional-inspired approach, rather than object-oriented.

Most of the time I'm in Powershell which, thanks to Powershell Core, is now cross-platform and incredibly powerful. But I'm finding myself also using Nu more and more. In both shells I also use the Databricks CLI a lot. Want to check the status of jobs? Use the CLI. Want to upload and download data? Use the CLI. And so on.

Microsoft’s VS Code topped the list with 20K stars and probably one of the best code editors out there today, a difficult truth for many to accept 😅 Ofc, Powershell is also on the list with ~9K stars in 2021

@{ RootModule = 'MyModule.psm1' ModuleVersion = '{0}' CompatiblePSEditions = @('Desktop','Core') GUID = '37ab75a9-7190-43fa-a0cd-f3c492e6a9d0' Author = 'Thotaz' CompanyName = 'Unknown' Copyright = '(c) 2022 Thotaz. All rights reserved.' Description = 'This is a demo module that shows what a module manifest could look like.' PowerShellVersion = '5.1' FunctionsToExport = @({1}) CmdletsToExport = @() VariablesToExport = @() AliasesToExport = @({2}) DscResourcesToExport = @() FileList = @({3}) PrivateData = @{ PSData = @{ Tags = @("Demo", "Module") LicenseUri = 'https://github.com/PowerShell/PowerShell/blob/master/LICENSE.txt' ProjectUri = 'https://github.com/PowerShell/PowerShell' ReleaseNotes = @"

I'm a powershell nerd that barely knows some C# so I like to look through the Powershell Source Code and pretend I can understand it.

The ProviderBase adds these Note Properties in the WriteObject method.

the thread also links to this discussion: https://github.com/PowerShell/PowerShell/issues/9997

#Must be run as admin $version="7.2.1"; Invoke-WebRequest -Uri "https://github.com/PowerShell/PowerShell/releases/download/v$($version)/PowerShell-$($version)-win-x64.msi" -OutFile "$env:homepath\downloads\PowerShellLatest.msi"; $ArgsPS='/i "'+$env:homepath+'\downloads\PowerShellLatest.msi" /quiet /norestart'; start-process -FilePath msiexec.exe -ArgumentList $ArgsPS -Wait; Remove-Item "$env:homepath\downloads\PowerShellLatest.msi"; rv version; rv argsps; #Verify: $Apps= @() $Apps+=Get-ItemProperty "HKLM:\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\*" # 32 Bit $Apps+=Get-ItemProperty "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*" # 64 Bit $apps|?{$_.displayname -like '*PowerShell 7*'}|select displayname,displayversion,installdate rv apps;

https://github.com/PowerShell/PowerShell (85% C#)