Programming

17941 readers

134 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]

founded 2 years ago

MODERATORS

snowe

Ategon

[email protected]

Any nushell users out there? Is it worth learning and using as my defualt shell? (lm.paradisus.day)

submitted 3 days ago by [email protected] to c/programming

23 comments fedilink hide all child comments

For those of you unaware: https://nushell.sh/

This is by far the most unique shell out there, since it doesn't use raw text as output/input to command line calls, but instead an actual data structure. It's like if every CLI call returned a database table, in a way.

you are viewing a single comment's thread
view the rest of the comments

[–] brian 8 points 3 days ago (1 children)

worst case you're parsing command output like you would in bash, so you're not really worse off. I've got a handful of aliases that wrap commands I run often so I only dealt with parsing in the beginning. there are enough builtins that output structured data, or applications that have a json flag that it's still useful.

speaking of powershell, it's easy enough in nushell to write an alias that shells out to pwsh and calls ConvertTo-Json then from json on the nu side. that gives you plenty of extra commands that are structured, at least on windows

[–] [email protected] 4 points 3 days ago (2 children)

Why not just use Powershell then? It's been available for Linux for a long time. I use it for scripting quite often

[–] brian 4 points 3 days ago

bc nu does everything pwsh does, but without the odd and verbose syntax. their exceptions and error codes are two different systems and don't make sense by default. instead of making shell cmds easy to parse I find myself having to use dotnet versions of things, which would be fine if the syntax for that wasn't so terrible. nu still feels like a unix shell for the most part.

pwsh has its place, especially since it's default. I've written plenty of pwsh scripts at work for ci and the like. I can get over the verbose naming in a text editor. using it from a repl isn't my favorite experience

[–] Kissaki 2 points 2 days ago

I always had an aversion to PowerShell syntax.

They're certainly both object shells. If you're already familiar with PowerShell, there's probably no reason or need to switch. I'm not familiar with PowerShell enough to identify where else they differ.