nushell VS elvish

I've been using nushell as my daily driver shell for a while. It's still very much in development, but it's got some nice features, like Windows cross compatibility, proper data types, and syntax highlighting

Now, I guess the deeper question is ‶is the text-based, line-delimited, pipe-oriented, interaction model between programs that don't know each other still relevant″; and we have seen new, more structured, approaches being tested, for instance with PowerShell or NuShell.

You can install PowerShell on Linux now, if you like - or there's nushell: https://www.nushell.sh/

I'll add the long awaited support for nushell in broot.

But that and xplr are both programs used within the shell and don't address that the shell is still outputting plain-dumb-dataless-text. https://www.nushell.sh/ promotes right on the homepage Everything is data so it's exciting to see and hope for a better future!

I don't understand what you mean by Graphics integration or graphical frontend. Do you have an example? Instead of du - I recommend dust. The data features - are basically the features of nushell, are you using it? Regarding the variables - excellent idea, I will implement this. What do you mean by menu creation? What syntax would you use for "skip next line"?

> Different components can integrate and coordinate through standards.

We've tried that and for the most part, it doesn't actually work in practice. Hell, it doesn't even work between standard Unix programs. They don't "integrate and coordinate" at all. They just push unstructured text around, and in some cases that's sufficient to perform some very basic compound tasks.

There is an upcoming project though that tries to make Unix pipelines work the way they are supposed to: Nushell[1]. It has real composability with strongly typed data that flows between commands.

Guess how they're doing it? Yup, that's right: They're building it all as a monolithic system where the entire pipeline is supervised and interpreted by the shell. Unix is too fragmented and standards are too difficult to develop and implement for any other approach to be realistically feasible. "Small programs" are an evolutionary dead end.

[1] https://www.nushell.sh/

Finally, I really do recommend looking into Nushell. It should give you a much better idea of how a shell could work if it weren't tied to ASCII blobs as its core data type.

If you're discontent with the state of shell scripting, you should give nushell a try: nushell.sh

If structured data is what excites you about pwsh, you should check out nushell: https://www.nushell.sh/. It is cross-platform like pwsh, and takes a similar approach to structured data, but has a much simpler syntax that I find more readable and much nicer to type than pwsh.

- https://github.com/elves/elvish

If you are looking for a more sane *shell* scripting language, Elvish looks promising: https://elv.sh/

Elvish: https://elv.sh/

I do this with elvish

Rivendell adds useful functionality to elvish to take your shell to the next level!

Compile elvish-shell

Elvish is a recent attempt at creating a better shell.

This is absolutely baffling in a shell, as of all the languages in existence, shell scripts simply have to support being piped to | head -n 5 and such! What's even the point of having Unix shell if you can't do something as simple. It looks like it was reported before, and closed without any fix. As far as I can tell, there's no way to even change that in options in Elvish the way you can in Ruby - there's no interface to operating system signals, and there are no specific exception types in Elvish, so if you wrap it in a try block, it will catch all exceptions.

Fuzzing is awesome. I just discovered an accidental O(2^n) code path in my project with fuzzing and fixed it: https://github.com/elves/elvish/commit/9cda3f643efafce2df567...

(In case people are curious, the project is a Unix shell, Elvish: https://elv.sh)