Maybe it's time we invent JPUs (json processing units) to equalize the playing field.
The best I can do is an ML model running on an NPU that parses JSON in subtly wrong and impossible to debug ways
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.
Hardware accelerated JSON Markov chain operations when?
Latest Nvidia co-processor can perform 60 million curly brace instructions a second.
60 million CLOPS? No way!
Until then, we have simdjson https://github.com/simdjson/simdjson
Well, do you have dedicated JSON hardware?
Please no, don't subsidize anything Java-Script. It will only make it less efficient.
And thus JsPU was born from Lemmy
NOOOOOOOO
Modern sites: This page requires a JsPU to run which is not present on this system. The website will run in reduced feature mode.
My thoughts on software in general over the past 20 years. So many programs inefficiently written and in 4th level languages just eats up any CPU/memory gain. (Less soap box and more of a curious what if to how fast things would be if we still wrote highly optimized programs)
Answer: there'd be far less software in the world, it would all be more archaic and less useful, and our phones and laptops would just sit at 2% utilization most of the time.
There's an opportunity cost to everything, including fussing over whether that value can be stored as an int instead of a double to save 8 bits of space. High level languages let developers express their feature and business logic faster, with fewer bugs, and much lower ongoing maintenance costs.
Even if our apps used resources better the adware will just use the free space.
Someone just needs to make a GPU-accelerated JSON decoder
That is sometime the issue when your code editor is a disguised web browser 😅
Everybody gangsta still we invent hardware accelerated JSON parsing
https://ieeexplore.ieee.org/document/9912040 "Hardware Accelerator for JSON Parsing, Querying and Schema Validation" "we can parse and query JSON data at 106 Gbps"
Render the json as polygons?
It's time someone wrote a JSON shader.
Ray TraSON
Rayson
Rockstar making GTA online be like: "Computer, here is a 512mb json file please download it from the server and then do nothing with it"
Reject MB, embrace MiB.
Reject MiB, call it "MB" like it originally was.
You've got them confused, MiB is the one misusing metric
Works fine in vim
CPU vs GPU tasks I suppose.
GPU, render my 4.2 MB json file!
Post funny things about programming here! (Or just rant about your favourite programming language.)
