zlacker

[return to "The Case for Nushell (2023)"]
1. adamne+Ko[view] [source] 2026-01-07 17:47:47
>>raveni+(OP)
I started using nushell around April 2024. While it is much better than other shell languages, the lack of proper types is painful.

Shell languages make sense if you believe in the Unix philosophy. For me, the problem with the Unix philosophy is the endless serialization and deserialization as well as lack of proper error handling. So nushell for me is a good answer to an ill-posed question.

The approach I have been taking is a single binary with a billion subcommands and aliasing these. I currently have two of these in Rust, one in Swift. I tried going all Rust but integrating with certain aspects of macOS is just so much simpler in Swift.

Like the recent push to make CLI development suck less (e.g. argument parsing used to be painful but is solved now) has made developing CLI tools a lot less painful.

◧◩
2. nialv7+4s[view] [source] 2026-01-07 17:59:23
>>adamne+Ko
serialization/deserialization will always be needed unless you got all your programs working with the same ABI. it's just that in nushell's case you aren't serialize to human readable text.
[go to top]