JSON: go with the standard "special delimiters" sounds brittle --> old fart loses nah. depends on context. given a large existing codebase that already has ef

JSON: go with the standard "special delimiters" sounds brittle --> old fart loses nah. depends on context. given a large existing codebase that already has effective communication implemented via special delimiters, recreating that same functionality in JSON really does not make much sense. ....sad though it is to say...