I just learned about nushell a few days ago and it blew me away. I’ve always wanted a shell that made manipulating data easier, and with my programming background the functional style just clicked instantly. Been daily driving it for a couple weeks, definitely recommend folks give it a go.
Yeah, same. For now I just drop into old reliable zsh when I need to l but I love nu so much I might go ahead and look into coming up with the stuff I miss myself.
It’s incredible, isn’t it? I’m already working on plugins for a variety of tasks so I can fire things off for malware analysis, push tables to data stores, and more. It’s such an obvious evolution of POSIX, I’m surprised it’s not already a standard across all shells.
Yup, it legit changed how I think about interacting with a shell. I’ve always been kinda terrible at actually learning stuff like awk, sed and company on the long term without needing half a dozen Google searches before they mostly do what I want so actually being able to perform complex operations on whatever input on the fly feels incredible!
It helps so much with API development as well, I’ve been using it on a side project and having a built-in http client plus auto JSON parsing feels ergonomic in ways that just make me giddy lol.
Sometimes I do some one liners when in a shell, and neither of these are POSIX compliant. That’s why I just stick to my customised zsh that basically does the same as fish.
You’re absolutely right. Fish isn’t really for scripting but is great for purely interactive use.
Nushell however offers a totally different approach to “scripting” and I can achieve far more in a nushell one-liner than I ever could in a POSIX shell as it’s far more comparable to Python Pandas than a shell.
For instance I can plot a line chart of file modifications over time directly in the shell with a single line of nushell. It’s mind blowing.
That’s great. I’m glad you like it and it sounds pretty awesome. It adds more variety to the command line, which is a beautiful thing. However, I do too much with remote systems that I don’t “own”, however, so, POSIX, for me, is a hard requirement - adding another domain specific language that I can only sometimes use is not worth the cognitive load for me.
That’s totally understandable. And I’ll admit, I’m still writing a fair few #!/bin/sh headed scripts as I to work on too POSIX systems. I think we’re a long long way off of the POSIX standard being superseded by something else.
Here’s a slightly better list. Call out to nushell and fish, my two modern shell favourites.
I just learned about nushell a few days ago and it blew me away. I’ve always wanted a shell that made manipulating data easier, and with my programming background the functional style just clicked instantly. Been daily driving it for a couple weeks, definitely recommend folks give it a go.
I discovered nushell a week ago and it’s my primary shell now too. I miss some completions tho
You can use carapace to get many of them
That’s really nice, thanks. Can’t wait to set it up on my machine.
Yeah, same. For now I just drop into old reliable zsh when I need to l but I love nu so much I might go ahead and look into coming up with the stuff I miss myself.
It’s incredible, isn’t it? I’m already working on plugins for a variety of tasks so I can fire things off for malware analysis, push tables to data stores, and more. It’s such an obvious evolution of POSIX, I’m surprised it’s not already a standard across all shells.
Yup, it legit changed how I think about interacting with a shell. I’ve always been kinda terrible at actually learning stuff like awk, sed and company on the long term without needing half a dozen Google searches before they mostly do what I want so actually being able to perform complex operations on whatever input on the fly feels incredible!
It helps so much with API development as well, I’ve been using it on a side project and having a built-in http client plus auto JSON parsing feels ergonomic in ways that just make me giddy lol.
Sometimes I do some one liners when in a shell, and neither of these are POSIX compliant. That’s why I just stick to my customised zsh that basically does the same as fish.
You’re absolutely right. Fish isn’t really for scripting but is great for purely interactive use.
Nushell however offers a totally different approach to “scripting” and I can achieve far more in a nushell one-liner than I ever could in a POSIX shell as it’s far more comparable to Python Pandas than a shell.
For instance I can plot a line chart of file modifications over time directly in the shell with a single line of nushell. It’s mind blowing.
That’s great. I’m glad you like it and it sounds pretty awesome. It adds more variety to the command line, which is a beautiful thing. However, I do too much with remote systems that I don’t “own”, however, so, POSIX, for me, is a hard requirement - adding another domain specific language that I can only sometimes use is not worth the cognitive load for me.
That’s totally understandable. And I’ll admit, I’m still writing a fair few #!/bin/sh headed scripts as I to work on too POSIX systems. I think we’re a long long way off of the POSIX standard being superseded by something else.
Fish is overrated imo.
Nushell is better but not quite what I’m looking for.