The bigger question is, what is there to be done? What is the road to a more uniform handling of JSON? I've handled some JSON before and it's usually fairly easy untill you catch one of these strange implementation quirks. But I'm not sure that those quirks can be ironed out at this point.
Can you help me understand the problem? These things seem like corner cases that you could just Not Do(TM) and then you don’t have to worry about it.
What am I missing, when do these gotchas become an actual problem for you as a developer?
I’m not sure I’ve used any technology that was free of footguns, and JSON appears to have fewer of them than the average programming language or library.
I call this kind of answer “The C Answer”. “Who cares if this particular combination of code results in undefined behavior? Just don’t do it!”
> when do these gotchas become an actual problem for you as a developer?
Whenever you have to deal with JSON produced by “not you”, or when you have to deal with JSON that may have been corrupted in some fashion along the way.
I’m probably just not used to pure “all behavior is defined” systems, so I appreciate your perspective.
What industry do you work in? I don’t see many systems like that in my industry. I work like hell to push things in that direction, but it’s a best case of “we went from 5% well defined behavior to 50%” after many years of effort.
