50 million rendered polygons vs one spicy 4.2MB boi

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

Well, do you have dedicated JSON hardware?

Everybody gangsta still we invent hardware accelerated JSON parsing

Render the json as polygons?

Permanently Deleted

That is sometime the issue when your code editor is a disguised web browser 😅

there are simd accelerated json decoders

CPU vs GPU tasks I suppose.

Would you rather have 100,000 kg of tasty supreme pizza, or 200 kg of steaming manure?

Choose wisely.

I have the same problem with XML too. Notepad++ has a plugin that can format a 50MB XML file in a few seconds. But my current client won't allow plugins installed. So I have to use VS Code, which chokes on anything bigger than what I could do myself manually if I was determined.

Someone just needs to make a GPU-accelerated JSON decoder

Works fine in vim

Reject MB, embrace MiB.

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"

Let it be known that heat death is not the last event in the universe

You jest, but i asked for a similar (but much simpler) vector / polygon model, and it generated it.

The obvious solution is parsing jsons with gpus? maybe not...

C++ vs JavaScript

I've never had any problems with 4,2 MB (and bigger) json files. What languages/libraries/editors chokes on it?

Given it is a CPU is limiting the parsing of the file, I wonder how a GPU-based editor like Zed would handle it.

Been wanting to test out the editor ever since it was partially open sourced but I am too lazy to get around doing it