Programmer Humor

32453 readers

317 users here now

Post funny things about programming here! (Or just rant about your favourite programming language.)

Rules:

Posts must be relevant to programming, programmers, or computer science.
No NSFW content.
Jokes must be in good taste. No hate speech, bigotry, etc.

founded 5 years ago

MODERATORS

AgreeableLandscape@lemmy.ml

cat_programmer@lemmy.ml

252

Surely "1337" is the same as 1337, right? (sopuli.xyz)

submitted 4 months ago by bleistift2@sopuli.xyz to c/programmerhumor@lemmy.ml

29 comments fedilink hide all child comments

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

you are viewing a single comment's thread
view the rest of the comments

[–] ApexHunter@lemmy.ml 11 points 4 months ago (1 children)

The joke is that, regardless of how the type is declared in json, you are parsing a string. (your json blob is just a series of characters, not raw binary data)

[–] Zucca@sopuli.xyz 2 points 4 months ago

Yes. And many people here doesn't seem to get that.

I'm not a dev of any kind. I occasionally write some bash and awk scriots to automate some things and if I need some kind of plain text (non-binary) data format I prefer tsv over json.

So why do I still get this? Is it just that many json advocates want to make sure others know json does support other data types than plain string?