nushell VS jq

Most of the time I'm in Powershell which, thanks to Powershell Core, is now cross-platform and incredibly powerful. But I'm finding myself also using Nu more and more. In both shells I also use the Databricks CLI a lot. Want to check the status of jobs? Use the CLI. Want to upload and download data? Use the CLI. And so on.

There are also some new shells in the list, including Tabbyand Nushell, which both had around 7K stars, though Nushell is a much newer project

I'd recommend to take a look at https://www.nushell.sh/ which has structured output, but displays it neatly when printing to the terminal.

I'm surprised to see no mention of nushell [0] I've tried it a while ago and seemed really promising

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

Has anyone tried out Nushell recently? I've been playing with it for the last few days, and it's shaping up into something pretty impressive for data/pipeline handling.

But no, people should use pipes in Nushell, of course! ;-P

Might want to add something about why someone would want this over something like say NuShell. Only thing I'm seeing right now seems to be the Lua thing.. which is kind of irrelevant to me anyway. Thanks.

You might find this interesting

There's also Nushell, which I've never used, which is similar to Powershell in that commands return structured data rather than text, but I believe has a more functional-inspired approach, rather than object-oriented.

jq is an open-source command line tool for interacting with JSON data, you can find the repository here and installations instructions for your system here.

Whilst the Databricks CLI is useful, there's times where I want a little more power over it. Such as, using the CLI to find a Databricks runtime version which is under Long Term Support (LTS) and is Photon enabled. So, I can do this using, for instance, the Databricks CLI and some jq. But I'm also lazy and wanted something that's a bit easier to query, and displays nicer, and is easier to output to something like CSV afterwards.

In today's world of excellent CLI tools I don't think grep is a good choice, especially for checking irregular languages like XML. [0]

I use tools like `jq` [1] or `yq` [2] all the time for CI checks. One useful check, is we have a configuration file stored as several hundred lines of YAML. Its a nice thing to maintain a sorted order for that, so we have a git pre-commit hook that runs the following:

> yq eval --inplace '.my_key|= sort' my_file.yaml

Of course, a pre-commit hook or CI both work. There's pros and cons of both. For our team, the pre-commit hook is a low enough level of effort, and doesn't require a CI check for something that executes in milliseconds.

[0] https://stackoverflow.com/a/1732454

[1] https://github.com/stedolan/jq

[2] https://github.com/mikefarah/yq

JQ makes using JSON much, much easier.

jq

Don't put binaries in your repo. (jq). You need to abide by the license for jq here https://github.com/stedolan/jq/blob/master/COPYING

The file can be processed with jq [https://stedolan.github.io/jq/], I had to invoke it as "jq . 133957095_NewYorkPresbyterianHospital_standardcharges_12312020_Updated07232021.json". But it should work to look up a CPT and get the cost.

The one thing I'd suggest is using the json output, and a tool like miller or jq to collate them into something like csv.

Wasn't a fan of JSON until I discovered jq either. Now I use it a lot.