From: Aharon Robbins <arnold@skeeve.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] More 'Sam I am'
Date: Fri, 10 Feb 2006 14:28:27 +0200 [thread overview]
Message-ID: <200602101228.k1ACSRL1020284@skeeve.com> (raw)
> Date: Fri, 10 Feb 2006 12:05:55 +0100
> From: uriel@cat-v.org
> Subject: Re: [9fans] More 'Sam I am'
> To: 9fans@cse.psu.edu
>
> > to process XML type data in the more traditional Unixy fashion.
> Oxymoron.
>
> uriel
Not at all. As the old saw goes,
When life hands you lemons, make lemonade.
Those of us who live in The Real World (tm) sometimes have no choice as to the
format the data we must process is received in, or alternatively, the format
in which it must be delivered. In such a case, I'd rather have a tool that
makes said format palatable to work with.
I happen to agree with rob's view of the whole XML thing. But if I find myself
in a situation where I have no choice but to work in some kind of XML, then
I'd sure rather turn to an awk-based solution than some gosh-awful mutant
buzzword hybrid.
Arnold
next reply other threads:[~2006-02-10 12:28 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-10 12:28 Aharon Robbins [this message]
2006-02-10 12:51 ` Dave Lukes
2006-02-10 14:04 ` Wes Kussmaul
2006-02-10 16:15 ` Skip Tavakkolian
2006-02-10 17:22 ` Wes Kussmaul
2006-02-10 17:41 ` Skip Tavakkolian
2006-02-10 18:21 ` Wes Kussmaul
2006-02-10 20:32 ` Lyndon Nerenberg
2006-02-11 4:36 ` Marina Brown
2006-02-11 4:39 ` Lyndon Nerenberg
2006-02-11 5:06 ` jmk
2006-02-11 6:52 ` lucio
2006-02-10 15:17 ` uriel
2006-02-10 17:42 ` Bakul Shah
-- strict thread matches above, loose matches on Subject: below --
2006-02-24 13:36 quanstro
2006-02-24 13:49 ` Anselm R. Garbe
2006-02-24 14:24 ` Gabriel Ivanes
2006-02-24 0:55 quanstro
2006-02-24 3:46 ` yard-ape
2006-02-24 4:40 ` Lucio De Re
2006-02-25 7:43 ` Serge Gagnon
2006-04-24 18:05 ` Serge Gagnon
2006-02-11 4:48 quanstro
2006-02-11 11:22 ` Bruce Ellis
2006-02-11 3:40 quanstro
2006-02-11 0:10 quanstro
2006-02-11 3:01 ` jmk
2006-02-10 16:49 quanstro
2006-02-10 15:22 quanstro
2006-02-10 14:09 quanstro
2006-02-10 14:15 ` Bruce Ellis
2006-02-10 15:17 ` John Stalker
2006-02-10 13:44 quanstro
2006-02-10 13:57 ` Bruce Ellis
2006-02-08 4:34 Lyndon Nerenberg
2006-02-08 5:29 ` Russ Cox
2006-02-08 5:51 ` Lyndon Nerenberg
2006-02-08 6:14 ` Russ Cox
2006-02-08 6:30 ` Lyndon Nerenberg
2006-02-08 6:46 ` geoff
2006-02-08 6:50 ` Lyndon Nerenberg
2006-02-08 17:31 ` Dan Cross
2006-02-08 18:14 ` Lyndon Nerenberg
2006-02-08 21:28 ` Dan Cross
2006-02-10 9:47 ` Aharon Robbins
2006-02-10 10:45 ` Steve Simon
2006-02-10 14:40 ` Dan Cross
2006-02-10 22:53 ` lucio
2006-02-23 22:52 ` Victor Nazarov
2006-02-10 11:05 ` uriel
2006-02-10 12:59 ` Bruce Ellis
2006-02-08 18:20 ` uriel
2006-02-08 19:50 ` Bruce Ellis
2006-02-08 21:35 ` Dan Cross
2006-02-08 21:43 ` Ronald G Minnich
2006-02-08 22:57 ` Christoph Lohmann
2006-02-09 0:03 ` Dan Cross
2006-02-09 0:17 ` Christoph Lohmann
2006-02-09 0:26 ` Dan Cross
2006-02-09 0:43 ` Christoph Lohmann
2006-02-09 1:11 ` andrey mirtchovski
2006-02-09 1:47 ` Christoph Lohmann
2006-02-09 1:56 ` Marina Brown
2006-02-09 2:35 ` Federico Benavento
2006-02-09 7:34 ` Bruce Ellis
2006-02-09 20:11 ` Ronald G Minnich
2006-02-09 16:06 ` Dave Eckhardt
2006-02-09 22:44 ` Marina Brown
2006-02-09 23:06 ` Bakul Shah
2006-02-10 1:37 ` Micah Stetson
2006-02-08 22:58 ` Lyndon Nerenberg
2006-02-09 13:04 ` LiteStar numnums
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200602101228.k1ACSRL1020284@skeeve.com \
--to=arnold@skeeve.com \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).