Live data from Hacker News

Nushell: Introduction to a new kind of shell

dataswamp.org

41–50 of 252 posts

Re: Nushell: Introduction to a new kind of shell

#41
post #35

>This is just an example from YAML to JSON, but you can convert much more formats into other formats. >open dev/home-impermanence/tests/impermanence.yml | to json I can do it with PowerShell: $os_list = (Get-Content -Path "C:\temp\operating-systems.yml" | ConvertFrom-Yaml) Set-Content -Path "C:\temp\PowerShell_operating-systems.json" -Value ($os_list | ConvertTo-Json)

Powershell is also quite anti-semantic, non-portable and verbose

> anti-semantic

Why?

> non-portable

PowerShell 6 and later run on Windows, macOS, and Linux.

> verbose

This is by design.

Re: Nushell: Introduction to a new kind of shell

#44

Should probably be switched to the official project page rather than a subpage on an unrelated party website: https://www.nushell.sh/ It’s a lot better at introducing Nushell and feels like a proper landing page.

So HN is not supposed to allow blog posts about projects but must always swap out for the project site itself? As someone who writes blog posts about projects, I hope not! It's not like this blog post is affiliate spam.

Re: Nushell: Introduction to a new kind of shell

#45

Should probably be switched to the official project page rather than a subpage on an unrelated party website: https://www.nushell.sh/ It’s a lot better at introducing Nushell and feels like a proper landing page.

It's a blog post but somehow the styling doesn't make it look like one.

Re: Nushell: Introduction to a new kind of shell

#46

Should probably be switched to the official project page rather than a subpage on an unrelated party website: https://www.nushell.sh/ It’s a lot better at introducing Nushell and feels like a proper landing page.

Better not. In this case the blog post provides more complex and interesting examples than the simplistic ones on the official page.

Re: Nushell: Introduction to a new kind of shell

#47
It'd be useful if there was some site detailing and benchmarking the size, overhead, performance etc. of the various popular shells on different systems. This looks interesting but the binaries seem rather large relative to bash. For example, what do the developers view as the minimal system parameters needed to avoid annoying latency?

Re: Nushell: Introduction to a new kind of shell

#48

I use it as my primary driver, for the sole reason is that it's the only cross-platform shell that properly supports Windows (without resorting to Cygwin/MSYS, which has performance issues and many pain points). I'm still getting used to the syntax though... (Edit: forgot to mention Powershell, since nowadays it also works on Macs and Linux)

Why use this over PowerShell for example?

No need for (a minimal set of) dotnet runtime. This means Nushell can possibly run on slightly resource constrained environment such as Raspberry Pi, of course you don't expect it to run well with 256MB of RAM though. Also, Nushell is battery packed. For example, say bye bye to your Oh-my-ZSH because the features you have with OMZ (like shell autocompletion, suggestion, theming and formatting) is built-in in Nushell. I have also tried to parse `zfs list` output in my Proxmox machine that I don't want to use `zfs list | less` that often.

That said, I hope Powershell Core can be packed with dotnet 7 native AOT mode [1] so we don't have to screw around with 100 different MSIL DLL files to run a single shell...

[1]: https://learn.microsoft.com/en-us/dotnet/core/deploying/nati...

Re: Nushell: Introduction to a new kind of shell

#49

Should probably be switched to the official project page rather than a subpage on an unrelated party website: https://www.nushell.sh/ It’s a lot better at introducing Nushell and feels like a proper landing page.

haha, thanks for this. i was looking at the examples on the other page and was like, "jfc, no thanks"

It's someone's personal blog post. No need to be mean. The styles are a little brutalist but also readable to me.

Re: Nushell: Introduction to a new kind of shell

#50

I use it as my primary driver, for the sole reason is that it's the only cross-platform shell that properly supports Windows (without resorting to Cygwin/MSYS, which has performance issues and many pain points). I'm still getting used to the syntax though... (Edit: forgot to mention Powershell, since nowadays it also works on Macs and Linux)

Why use this over PowerShell for example?

It's more Unix-y. Smaller footprint, opens faster, short commands by default. Otherwise the PowerShell influence is vastly understated in project page and docs.
Post reply on HN