Who is going to read this information anyway?
Who is going to read this information anyway?
Posted Apr 20, 2009 0:27 UTC (Mon) by xoddam (guest, #2322)In reply to: What's coming in glibc 2.10: XML by bvdm
Parent article: What's coming in glibc 2.10
Heap implementation and performance details are not the sort of thing an application can hope to comprehend and adapt to on the fly. I would expect this information to be examined only by developers (often after the fact eg. in logs depicting memory pressure in a production system experiencing performance problems or horrible OOM events), who might prefer a more human-readable representation but shouldn't be afraid of XML in the case of a complex hierarchical heap structure.
Posted Apr 20, 2009 19:41 UTC (Mon)
by jkohen (subscriber, #47486)
[Link]
If you want structured data ready for human consumption, you probably need to write a user-space tool, in which case using XML is no better than protocol buffers, JSON and so on; it just has a more complicated spec.
Who is going to read this information anyway?
In this case there is really no excuse to go with XML. Even something like /proc/meminfo is more readable to a human than structured markup.