I have tried out nushell for a couple of months. I was drawn to the piping commands like <code>where</code> , <code>split</code> and so on. I also enjoyed the color output and dealing with output as data - in practice though, this just didn’t come in handy that often.
There were also a few things from fish that I started to sorely miss:
<ul>
<li>ALT+Arrow to go to previous/next directories</li>
<li>The math command</li>
</ul>
There are several things that don’t work in nushell on my system, and I found myself constantly switching to other shells to accomplish tasks. I’m sure that I could eventually get it working in nushell, but I didn’t find the time and had already sunk a lot into the learning curve, I thought, for a shell.
It will make more sense for me then, to not have nushell as my primary shell, rather I’d switch to it should I want to use some of its commands which is much less common for me.
A larger issue arose in using nushell though, one of a fundamental nature.
The commands it has inevitably would cause someone to lose their skills in the core utils. It is a layer of abstraction. You don’t have to use their abstractions, but then why even use nushell if you’re not.
Maybe core utils doesn’t matter to some, but to me it still does because I am doing remote work on servers often where installing whatever you want is sometimes not an option.
So, I liked the concept, and may even revisit it some day when I have more time, but as for now I’m going back to fish.

After trying Nushell for several months, the author is switching back to Fish shell. While Nushell's data-oriented piping commands and color output were appealing, they proved less useful in practice. Missing Fish features like ALT+Arrow directory navigation and compatibility issues led to frequent shell switching. The fundamental concern is that Nushell's abstractions over core utilities could erode essential skills needed for remote server work where custom shell installation isn't always possible.

Nushell? Notnow