Re: Suggested dual human/binary interface for proc/devfs

From: Ed Carp (erc@pobox.com)
Date: Tue Apr 11 2000 - 02:16:05 EST


Bill Wendling (wendling@ganymede.isdn.uiuc.edu) writes:

> Also sprach Ed Carp:
> } Terje Kvernes (terjekv@ifi.uio.no) writes:
> }
> } > personally I'd like to see procdump at least not produce html, it
> } > should instead produce XML and one should have a nice XSL to go with
> } > that. but I digress. (this should exist no matter how one chooses to
> } > display the information to users of course ,)
> }
> } No, no, NO! Straight ASCII. Forget the latest XML/XSL BS/hype.
> }
> } Why is it that people who should know better always jump on the latest
> } and greatest technological whizz-bang like it's the silver bullet that
> } will cure all ills?
> }
> Have you ever used XML? It's actually quite useful for a number of
> things. It's based off of SGML, which has been around for quite a while.
> And it has a number of really nice features.

Yes, I have. I've written programs that generate XML. Several of them, in fact.

> Why are you so violent against its use?

For the same reason I'm "violent" against the use of anything that's not EASILY machine parseable. THINK SIMPLE, Bill.

<DEVICE>
eth0
<IP_ADDRESS>
192.168.201.116
</IP_ADDRESS>
</DEVICE>

or

device {
eth0
ip_address {
192.168.201.116
}
}

is a complete and total waste of computer cycles to parse with a script, not to mention a pain in the patootie.

But:

device=eth0;ip_address=192.168.201.116,netmask=255.255.255.0

for example, is a LOT easier for a script to parse and use. Add a little whitespace and it's a lot easier for humans to parse, too.

Why are people so damned insistent on making this thing as hard as possible to do? Is it sexier or something to make it difficult?

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/



This archive was generated by hypermail 2b29 : Sat Apr 15 2000 - 21:00:15 EST