3 ms·
My first step is https://concise-encoding.org https://concise-encoding.org All of this constant stringification/destringification just for another machine to r
by kstenerud 6y ago
My first step is https://concise-encoding.org https://concise-encoding.org
All of this constant stringification/destringification just for another machine to read some transmitted data is massively wasteful, but we all do it because we want our data to be human readable, so we use JSON. But what if you could send as binary, with the ability to convert 1:1 to/from text only when you needed a human to inspect or input the data?
What if you didn't need to encode all of your non-numeric data into strings?
I've got many other steps in the pipeline to reduce our energy wastage, but this first one has taken awhile (3 years), and I still need more eyes on it to make sure nothing gets missed before I release in a few months.
- layoutIfNeeded 6y agoSomeone cue in the appropriate xkcd about n+1 standards.
- harshitaneja 6y agoProtobuf?
- kstenerud 6y agoProtobuf is solving a different problem than the JSON, BSON, XML style ad-hoc data encodings. It's also not human readable.