A collection of modern/faster/saner alternatives to common unix commands. - GitHub - ibraheemdev/modern-unix: A collection of modern/faster/saner alternatives to common unix commands.
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.
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.