NIP itself is pretty hackish, it's going to have to give way to something more organised and meritocratic at some point

being that I'm implementing a base set of parsers for them I can attest that the specifications have many missing stipulations that are assumed into existence by common JSON encoders that defy expectations from someone not experienced with JSON especially javascript JSON and the most popular encoders for C++, Rust, etc, and many of those are outside of the expectations of Go programers who are used to stringently static typing and no wibbly wobbly union and underspecified variadic structures