A Journey building a fast JSON parser and full JSONPath

Is JSON XML yet? Nearly!<p>I’m going to invent Baz’s 11th law of computing here: any data format that isn’t XML will evolve into a badly specified version of XML over time.

Slightly tangential, but Go&#x27;s JSON handling has long had room for improvement and it looks like there&#x27;s going to be a serious overhaul of its capabilities and implementation: <a href="https:&#x2F;&#x2F;github.com&#x2F;golang&#x2F;go&#x2F;discussions&#x2F;63397">https:&#x2F;&#x2F;github.com&#x2F;golang&#x2F;go&#x2F;discussions&#x2F;63397</a> -- I&#x27;m looking forward to seeing this land.

We all know the builtin golang JSON parser is slow.<p>How about doing comparisons against other implementations?<p>Like this one: <a href="https:&#x2F;&#x2F;github.com&#x2F;json-iterator&#x2F;go">https:&#x2F;&#x2F;github.com&#x2F;json-iterator&#x2F;go</a><p>Update: found this outdated repo: <a href="https:&#x2F;&#x2F;github.com&#x2F;ohler55&#x2F;compare-go-json">https:&#x2F;&#x2F;github.com&#x2F;ohler55&#x2F;compare-go-json</a>

reminder of recent efforts at standardizing JSONPath: <a href="https:&#x2F;&#x2F;datatracker.ietf.org&#x2F;wg&#x2F;jsonpath&#x2F;about&#x2F;" rel="nofollow noreferrer">https:&#x2F;&#x2F;datatracker.ietf.org&#x2F;wg&#x2F;jsonpath&#x2F;about&#x2F;</a>

Nice work! I see that that this is for processing &#x2F; parsing large data sets and where documents do not conform to a fixed structure and for Go language.<p>I made something similar in Java - unify-jdocs - <a href="https:&#x2F;&#x2F;github.com&#x2F;americanexpress&#x2F;unify-jdocs">https:&#x2F;&#x2F;github.com&#x2F;americanexpress&#x2F;unify-jdocs</a> - though this is not for parsing - it is more for reading and writing when the structure of the document is known - read and write any JSONPath in one line of code and use model documents to define the structure of the data document (instead of using JSONSchema which I found very unwieldy to use) - no POJOs or model classes - along with many other features. Posting here as the topic is relevant and it may help people in the Java world. We have used it intensively within Amex for a very large complex project and it has worked great for us.

I like the &quot;Simple Encoding Notation&quot; (SEN) of the underlying library: <a href="https:&#x2F;&#x2F;github.com&#x2F;ohler55&#x2F;ojg&#x2F;blob&#x2F;develop&#x2F;sen.md">https:&#x2F;&#x2F;github.com&#x2F;ohler55&#x2F;ojg&#x2F;blob&#x2F;develop&#x2F;sen.md</a><p>&quot; A valid example of a SEN document is:<p>{ one: 1 two: 2 array: [a b c] yes: true } &quot;