From: kazumi iwane <kiwane@mx6.ttcn.ne.jp>
To: 9fans@cse.psu.edu
Cc: plan9@blueyonder.co.uk
Subject: Re: [9fans] OT: DTD to yacc spec?
Date: Fri, 20 Feb 2004 03:20:05 +0900 [thread overview]
Message-ID: <3E1485B2-6308-11D8-B491-000393CBA46C@mx6.ttcn.ne.jp> (raw)
In-Reply-To: <d2090d153502fe41a9e7e2c2622fb542@tombob.com>
> I guess this kind of thing is just a fallout from discussions that end
> up in "we have all these homegrown file formats for configuration,
> user preferences, application private data, ..., and it must be so
> much hassle keeping all of that coded up nicely; we need to clean this
> up pronto, and the only recognised way of doing it is by using XML;
> our life will become so much simpler, as there are so many tools out
> there to help with this." Sniff.
Sounds very familiar. We use XML only because everybody else
does. This silly reasoning hardly justifies the cost of dealing with
complexity forced upon us by XML parsers.
-- kazumi
next prev parent reply other threads:[~2004-02-19 18:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-19 16:31 kazumi iwane
2004-02-19 17:08 ` plan9
2004-02-19 17:19 ` David Tolpin
2004-02-19 18:23 ` kazumi iwane
2004-02-19 18:20 ` kazumi iwane [this message]
2004-02-20 2:44 ` boyd, rounin
2004-02-19 17:47 Laura Creighton
2004-02-19 18:25 ` kazumi iwane
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=3E1485B2-6308-11D8-B491-000393CBA46C@mx6.ttcn.ne.jp \
--to=kiwane@mx6.ttcn.ne.jp \
--cc=9fans@cse.psu.edu \
--cc=plan9@blueyonder.co.uk \
/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).