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

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…”

116 comments

To whoever does that, I hope that there is a special place in hell where they force 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.

Sincerely, a frustrated Rust dev
"1" + "1"
These JSON memes got me feeing like some junior dev out there is upset because they haven't read and understood the docs.
I'll have you know all of my code is stringly typed.
CBOR for life, down with JSON.
Explicit types are just laziness, you should be catching exceptions anyways.
A string that represents types...
It's the API's job to validate it either way. As it does that job, it may as well parse the string as an integer.
json doesn't have ints, it has Numbers, which are ieee754 floats. if you want to precisely store the full range of a 64 bit int (anything larger than 2^53 -1) then string is indeed the correct type
This is String - you’ve seen it before haven’t you, Gollum?
The comment section proves that xml is far superior to json
Protocol Buffers are hated, but they are needed.

You've viewed 116 comments.