I feel like many of the points are complaining about the parsing side of JSON. Not the format itself.
You can argue that a format is useless when "everyone" parses it "wrong" but no specification on this earth is free of that.
Using a lot of json in our API space and it working fine (so far) leads me to think that OP complains about something that does not fit their use-case.
Firing people for choosing something that does not fit "your" use-case seems like a wild take.
Using a lot of json in our API space and it working fine (so far) leads me to think that OP complains about something that does not fit their use-case.
Firing people for choosing something that does not fit "your" use-case seems like a wild take.