I realize that there are 1001 alternatives to JSON encoding, that are leaner, faster, or just completely different, but I still have my own that I'd like to share.
LOEN stands for Lean Object Encoding Notation and aims to reduce the character count compared to JSON, especially in the case of arrays of objects; JSON is crazy verbose in this regard, and so using an alternative when transmitting lists or database results, is pretty much a must-do.
Other than being lean, the MVP of LOEN is that it is backwards compatible with JSON. JSON is valid LOEN but not the other way around. This is useful in that it allows for a LOEN interpreter to be used for both LOEN and JSON requests. If by magic LOEN were to become commonplace, it would allow for legacy apps using JSON to continue to function.
Anyway not expecting anything but happy to here what you think.
LOEN stands for Lean Object Encoding Notation and aims to reduce the character count compared to JSON, especially in the case of arrays of objects; JSON is crazy verbose in this regard, and so using an alternative when transmitting lists or database results, is pretty much a must-do.
Other than being lean, the MVP of LOEN is that it is backwards compatible with JSON. JSON is valid LOEN but not the other way around. This is useful in that it allows for a LOEN interpreter to be used for both LOEN and JSON requests. If by magic LOEN were to become commonplace, it would allow for legacy apps using JSON to continue to function.
Anyway not expecting anything but happy to here what you think.
Here's an article I wrote about it: https://www.offthebricks.com/articles/lean-object-encoding-a...
Here's a link to the GitHub repo: https://github.com/offthebricks/LOEN/tree/master