This is fun, but reading the commands[1] reminds me of learning a new language. There are just too of them, and they are all pipelined in a functional manner so I need to understand the I/O of them. In that case, why would one bother remembering all of those, when Xonsh or IPython does similar job to their data, only with a few more lines of (more familiar) code?
I don't think you need to remember all of Nushell's commands (I certainly don't). You can go far with a handful of important ones; off the top of my head, get/select/where/sort-by/open are the most important.
This is something we should communicate better in the docs, I'll see what I can do.
I have written a bunch of nu and: no dot method syntax means you need to browse documentation for literally everything. So much worse than your average programming language, which takes the data type + you enter a dot = it suggests all the relevant methods. The Nu docs are better than they were a few years ago but as far as I can tell they keep changing command names, having subtle changes of behaviour for commands with the same name but apparently different implementations for different data types, having a crucial command listed under a weird name that takes an hour to find, etc etc. If I need to wrangle some JSON again I think I’ll just use Python.
[1]: https://www.nushell.sh/commands/