Anybody have a good breakdown of the philosophical/implementation differences between nushell and oil?
After using PowerShell at a job recently I'm interested in dipping my toe into using these kinds of projects, but my websearch skills seems like they're getting worse these days, haven't found a good comparison yet.
Nushell seems like it's really its own thing. It works with commands that output tabular data (and provides tabular versions of the most popular commands) and then provides functions to query that data. It's more of a query language in your shell than a regular old shell language.
I use nushell as my daily driver but I've tried a few "alt" shells over the years, from fish to xonsh and now nushell.
oil is really two different languages, OSH and YSH. OSH is basically aimed at replacing bash with little to no code changes, just less idiosyncrasies in the interpreter. If you like the idea of using shell scripts for building/controlling critical components but hate the idea of using ([db]?a)?sh then osh is probably a good option. I have not personally used YSH as a daily driver shell.
xonsh is aimed at people who like Python so much that they want to have a Python-esque shell and it's quite nice, although sometimes it's not exactly obvious when you should switch to raw Python eval mode when it comes to the nitty-gritty (or should you just write a Python script at that point?).
fish is really nice, specifically aimed at interactive use. Includes a lot of features out of the box. If you're looking to try any interactive shell, I recommend starting with fish. I've come very close to switching back to fish during my adventures with both xonsh and nushell. Subprocess support is.. As far as I know, still quite lacking. There are workarounds for 90% of use-cases of subprocesses, though.
nushell could probably be described as heavily PowerShell inspired, but written in rust. The syntax has changed several times, it's quite experimental. One of the most annoying things about nushell is that it has built-ins that override things like ls, rm, etc. and you have to use ^ls ^rm etc. to break-out of that behaviour (or get used to the "nu" way). I believe the main reason for this is because nu pipelines aren't just working on streams of text. See https://www.nushell.sh/book/pipelines.html#behind-the-scenes for better explanation.
If you used PowerShell and simply enjoyed using PowerShell specifically, then you can also install pwsh on *nix. Perhaps the main downside is that most tutorials, modules etc. are written with Windows in mind, but as a shell it works perfectly fine.
Thanks, that's a great breakdown. I'm not too worried about libraries, as I try to avoid importing code willy nilly, but have you used pwsh extensively on nix? How powerful is the object/data model when it doesn't have access to COM/.NET/etc? Does it create integrations/reimplementations for distinctly nix things like device files? Or will I basically be writing a lot of compatibility layers to get raw text into structured data?
My use of non-Windows PowerShell is mainly used to sanity checking scripts that are destined to run on Windows boxes, where I want to quickly check the semantics of certain OS agnostics behaviour without firing up a remote desktop to a Windows VM.
work exactly as you'd expect them to on *nix. I don't have procfs on my system but I imagine that would work just the same as interacting with any other file.
PSDrive works the same as you would expect, including things like reading/manipulating ENV via the "Env:" PSDrive.
I can't think of anything off the top of my head that you can do in Bash that you couldn't do in PowerShell.
I know it's still kind of early days for nushell but recently, nushell has broken env/config format a couple of times.
If you use this as your main shell, that's annoying and frustrating. I know it's "ZeroVer" but I'd rather they at least warn first "this syntax will be unsupported in the next version" or something.
A shell can be like a second home, you don't want to upgrade your home only to find that a meteor has immediately crashed through the roof.
I wouldn't recommend trying nu unless you're willing to live on the bleeding edge, but if you're already on the bleeding edge, I would recommend using rustup to install rust and cargo to install nu (then you can use cargo-update to keep nu up to date).
Yes, brew works well on any x86 Linux distro (doesn't support ARM yet, sadly).
> Why is there no Debian or Ubuntu package or ppa listed?
Packaging for every distro is a lot of work, and the Nu core team has had other priorities. I think we'd like to have Debian-specific packages eventually but that will probably require some work by a motivated contributor. In the meantime we publish binaries, and it's fairly easy to build from scratch or use Homebrew.
After using PowerShell at a job recently I'm interested in dipping my toe into using these kinds of projects, but my websearch skills seems like they're getting worse these days, haven't found a good comparison yet.