JSON became an official standard in 2013, by which time many open-source, independent implementations existed. > I just don’t think there’s any rule that says

JSON became an official standard in 2013, by which time many open-source, independent implementations existed. > I just don’t think there’s any rule that says that we need multiple implementations of thing to make it a standard There are rules that say that we need multiple implementations of thing to make it a standard: * The IETF requires it to be accepted as "Internet standard", ie the highest form: https://en.wikipedia.org/wiki/Internet_Standard#Standardization_process https://en.wikipedia.org/wiki/Internet_Standard#Standardizat... * The W3C strongly desires that proposed standards have multiple, independent implementations to advance to the state of "Proposed reccomendation": https://www.w3.org/2005/10/Process-20051014/tr.html#cfr https://www.w3.org/2005/10/Process-20051014/tr.html#cfr > Also, we already have a standard for SQL and they could’ve just used the parts of SQLite that were compliant with that. That would probably have been the best solution, I agree. And then people would have complained about bloat again, that browsers are now required to expose a SQL engine, that they are too big, etc...