1335
you are viewing a single comment's thread
view the rest of the comments
[-] themoonisacheese@sh.itjust.works 283 points 4 months ago

Maybe it's time we invent JPUs (json processing units) to equalize the playing field.

[-] seaQueue@lemmy.world 216 points 4 months ago

The best I can do is an ML model running on an NPU that parses JSON in subtly wrong and impossible to debug ways

[-] Aceticon@lemmy.world 58 points 4 months ago

Just 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.

[-] seaQueue@lemmy.world 14 points 4 months ago

Hardware accelerated JSON Markov chain operations when?

[-] theterrasque@infosec.pub 8 points 4 months ago

So you're saying it's already feature complete with most json libraries out there?

[-] NigelFrobisher@aussie.zone 34 points 4 months ago* (last edited 4 months ago)

Latest Nvidia co-processor can perform 60 million curly brace instructions a second.

[-] ICastFist@programming.dev 5 points 4 months ago

Finally, something to process "databases" that ditched excel for json!

[-] JackbyDev@programming.dev 4 points 4 months ago

60 million CLOPS? No way!

[-] 0x0@lemmy.dbzer0.com 15 points 4 months ago
[-] ApeNo1@lemm.ee 9 points 4 months ago

JSON and the Argonaut RISC processors

this post was submitted on 14 May 2024
1335 points (100.0% liked)

Programmer Humor

32065 readers
491 users here now

Post funny things about programming here! (Or just rant about your favourite programming language.)

Rules:

founded 5 years ago
MODERATORS