jsoncrack.com VS murex

They are used in Editor component. Part 4 explains about Editor component.

useGraph has a lot going on, but we will look for setGraph as this is the side effect performed in setJson explained above.

In this post, let's understand the editor's Panes component used in jsoncrack.com.

Open src/pages/editor.tsx in a new tab and let’s take the top down approach. Let’s first look into the components used.

Visit GitHub

https://github.com/AykutSarac/jsoncrack.com As far as I can see they don't use any package to visualize, but I also need that package, if you find it please let me know!

looks a lot like JSON Crack with added support for additional formats and not being open-source

As we've seen in this article, there are many different tools available to help us work with JSON data. From visualizing and exploring data with JSON Crack, formatting it with JSON Formatter & Validator, converting it to other formats like CSV with Konklone.io, and validating it against a schema with JSON Schema — these tools can help make working with JSON data much easier and more efficient.

This is how murex works too https://github.com/lmorg/murex/blob/master/config/defaults/p...

I agree. I’ve written about this before but this is what murex (1) does. It reimplements some of coreutils where there are benefits in doing so (eg sed, grep etc -like parsing of lists that are in formats other than flat lines of text. Such as JSON arrays)

Mutex does this by having these utilities named slightly different to their POSIX counterparts. So you can use all of the existing CLI tools completely but additionally have a bunch of new stuff too.

Far too many alt shells these days try to replace coreutils and that just creates friction in my opinion.

1. https://murex.rocks

This is exactly what Murex shell does. It has lots of builtin tools for querying structured data (of varying formats) but also supports POSIX pipes for using existing tools like `jq` et al seamlessly too.

https://murex.rocks

Stable is a problem because a lot of these shells don’t offer any guarantees for breaking changes.

My own shell, https://github.com/lmorg/murex is committed to backwards compatibility but even here, there are occasional changes made that might break backwards compatibility. Though I do push back on such changes as much as possible, to the extent that most of my scripts from 5 years ago still run unmodified.

This is similar to how my shell works. It still just passes bytes around but additionally passes information about how those bytes could be interpreted. A schema if you will. So it works as cleanly with POSIX / GNU / et al tools as it does with fancy JSON, YAML, CSV and other document formats.

It basically sits somewhere between Powershell and Bash: typed pipelines like Powershell but without sacrificing familiarity with all the CLI commands you already use day in and day out.

https://github.com/lmorg/murex

As an aside, I’m about to drop a massive update in the next few days that will make the shell even more intuitive to use.