@hywan my issue with nushell (and powershell) is that as cool as passing typed objects between commands instead of plaintext streams is, it's simply less flexible. If everything takes and transforms text streams, absolutely anything that produces any kind of textual output is fair game for reaching into and manipulating and adding to the pipeline, as long as you know awk and regex sufficiently. With this, you're more limited to what the shell supports. Not only that, but this plus being a typed language makes nushell much more rigid. Which makes it a far better programming language, but a far worse shell — because the entire POINT of a shell is being a programming language that is *intentionally bad* in order to optimize for maximum flexibility and brevity and convenience for immediate tasks. Adding types and such actually de-optimizes the language for use as a shell. It's why no one wants to use like, Python or TypeScript as their shell!