You're viewing a single thread.
Maybe it's time we invent JPUs (json processing units) to equalize the playing field.
292 0 ReplyThe best I can do is an ML model running on an NPU that parses JSON in subtly wrong and impossible to debug ways
220 0 ReplyJust make it a LJM (Large JSON Model) capable of predicting the next JSON token from the previous JSON tokens and you would have massive savings in file storagre and network traffic from not having to store and transmit full JSON documents all in exchange for an "acceptable" error rate.
58 0 ReplyHardware accelerated JSON Markov chain operations when?
14 0 Reply
Permanently Deleted
55 0 ReplyDid you know? By indiscriminately removing every 3rd letter, you can ethically decrease input size by up to 33%!
5 0 Reply
So you're saying it's already feature complete with most json libraries out there?
8 0 Reply
Latest Nvidia co-processor can perform 60 million curly brace instructions a second.
34 0 ReplyFinally, something to process "databases" that ditched excel for json!
5 0 Reply60 million CLOPS? No way!
4 0 Reply
Until then, we have simdjson https://github.com/simdjson/simdjson
17 0 ReplyJSON and the Argonaut RISC processors
9 0 Reply