> I don't think this is a reasonable approach. That's just a way to introduce bloat.
Can this meme die already? The fact that out of the box install of Rust can’t parse JSON is a joke, and you know it.
Can this meme die already? The fact that out of the box install of Rust can’t parse JSON is a joke, and you know it.
On the other hand a change like this perf improvement can be released without tying it to a language version, that’s good too.
And you pay for that by having literally no way to parse something ubiquitous like json out of the box on install, relying to either installing third party lib (which is yet another security attack vector, requires yet another approval for upgrade, API can change on a whim by maintainer and other can of worms) or by using other language.
> requires yet another approval for upgrade
Approval from whom?
Rust is a systems programming language. If Rust had JSON support built in, I'd take it much less seriously. JSON is a fad, just like XML was 20 years ago. In 20 years, when JSON goes the way of XML, the Rust stdlib team should not have to continue maintaining a JSON parser.
An out of the box install of C can't parse JSON either. Do you think C is a joke? C++? Java?
How often does it even need to be updated to parse freaking json?
In production, I've lately seen serde_json backed python implementations, this makes sense for performance and memory safety.
serde_json = "*"