Hacker News new | ask | show | jobs
by zamadatix 2412 days ago
Referring to it in bytes purely serves to spread FUD. It's >100 levels of nesting which is a bit silly.
1 comments

I did that intentionally, and not because FUD. I hear ">100 levels of nesting", and think "huge document", which as demonstrated here isn't necessarily true. So I said "202 bytes" to emphasize "not huge document"; to emphasize that deep nesting doesn't really imply much about document size.
100+ levels of nesting implies nothing about the size of a JSON file, just that it's an extremely niche use case. OTOH almost all JSON files are 202+ bytes. Couple that with the title and it just leads to confusion.
>niche use case

Like an attack.