bleistift2Jun 30, 2024

Surely "1337" is the same as 1337, right?

https://sopuli.xyz/post/14326368

Surely "1337" is the same as 1337, right? - Sopuli

Meme transcription: Panel 1: Bilbo Baggins ponders, “After all… why should I care about the difference between int and String? Panel 2: Bilbo Baggins is revealed to be an API developer. He continues, “JSON is always String, anyways…”

Show threadRustyNovaJun 30, 2024
To whoever does that, I hope that there is a special place in hell where they for you to do type safe API bindings for a JSON API, and every time you use the wrong type for a value, they cave your skull in.
Show threadMubelotixJul 1, 2024
You HAVE to. I am a Rust dev too and I’m telling you, if you don’t convert numbers to strings in json, browsers are going to overflow them and you will have incomprehensible bugs. Json can only be trusted when serde is used on both ends
Show threadRustyNova
This is understandable in that use case. But it’s not everyday that you deal with values in the range of overflows. So I mostly assumed this is fine in that use case.
Jul 2, 2024 at 7:06amWeb