On Tue, Feb 5, 2019 at 11:18 AM Konrad Hinsen <konrad.hin...@fastmail.net> wrote: > > David Storrs <david.sto...@gmail.com> writes: > > > to type things. In addition, most developers that I've worked / > > talked with will typically reach for the JSON API before the XML one > > given the choice. I think the ground truth suggests that JSON is a > > Ah, I see, we are working in very different contexts. In a Web API, I'd > go for JSON as well. After all, you need little more than a > serialization format for the input and output parameters of the API functions. > > But my main use case is data storage in self-contained files stored in > databases (including Git repositories), to be read by existing or > yet-to-be-written software. The data can be quite complex, so any > machine-readable description of its structures is a plus. XML on its own > already provides the tag structure, and a schema adds much more > documentation, still in a standard format.
Ah, I see. So the answer to "What is a real-world case where it makes sense to use XML over anything else?" is "When storing data on disk."[1] Okay, I can get behind that. Thanks. [1] DBs are a special case of 'on disk'. > > Konrad. -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
