4 ms·
Did you even open the article? Following is literally in first paragraph > This package offers the same high level json.Decoder API but higher throughput and r
by bsdnoob 3y ago
Did you even open the article? Following is literally in first paragraph
> This package offers the same high level json.Decoder API but higher throughput and reduced allocations
- jcelerier 3y agoHow does that contradict what the parent poster says? I think it's very weird to call something "high performance" when it looks like it's maybe 15-20% of the performance of a simdjson in c++. This is not "going from normal performance to high performance", this going from "very subpar" to "subpar"
- willsmith72 3y agoOk but how many teams are building web APIs in C++?
- TheCleric 3y agoI worked with a guy who did this. It was fast, but boy howdy was it not simple.
- lolinder 3y agoPar is different for different stacks. It's reasonable for someone to treat their standard library's JSON parser as "par", given that that's the parser that most of their peers will be using, even if there are faster options that are commonly used in other stacks.
- Thaxll 3y agoBecause even in C++ people don't use json simd most project use rapidjson which Go is on part with.