While I am not a fan of Paul Graham, if this quote is read sarcastically, it's almost funny:
"If SETI@home works, for example, we'll need libraries for communicating with aliens. Unless of course they are sufficiently advanced that they already communicate in XML."
Because SETI@home and XML are always funny. I think.
I'm personally a sudden, suprising, recent convert to JSON, and if I cannot avoid XML in the future I Plan to use JsonML as my preferred representation.
"Any sufficiently complicated C program contains an ad hoc informally-specified bug-ridden slow implementation of half of Common Lisp." -- Philip Greenspun
I faced this problem three years ago. My management inststed on a format approved by an independent standards body with as much industry adoption as XML.
So each instance of the product I maintain has 100 kB of detailed configuration and state data in SQL INSERT statements. I've never had any support issues on it, unlike my coleagues who deal with products that use XML.
('cause hot damn i'm a gonna.)
While I am not a fan of Paul Graham, if this quote is read sarcastically, it's almost funny:
"If SETI@home works, for example, we'll need libraries for communicating with aliens. Unless of course they are sufficiently advanced that they already communicate in XML."
Because SETI@home and XML are always funny. I think.
this quote is surely the cousin of:
"Any sufficiently complicated C program contains an ad hoc informally-specified bug-ridden slow implementation of half of Common Lisp." -- Philip GreenspunRe: this quote is surely the cousin of:
I was going to guess, "Those who do not understand TCP are doomed to reinvent it, badly."Re: this quote is surely the cousin of:
I'm pretty sure you could replace "TCP" with a wildcard in that sentence.
So each instance of the product I maintain has 100 kB of detailed configuration and state data in SQL INSERT statements. I've never had any support issues on it, unlike my coleagues who deal with products that use XML.