From: Jon Masters <jonmasters@gmail.com>
To: Ahmad Reza Cheraghi <a_r_cheraghi@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Why no XML in the Kernel?
Date: Sun, 2 Oct 2005 19:53:15 +0100 [thread overview]
Message-ID: <35fb2e590510021153r254b7eb0haf9f9e365bed051e@mail.gmail.com> (raw)
In-Reply-To: <20051002094142.65022.qmail@web51012.mail.yahoo.com>
On 10/2/05, Ahmad Reza Cheraghi <a_r_cheraghi@yahoo.com> wrote:
> Can somebody tell me why the Kernel-Development dont
> wanne have XML is being used in the Kernel??
I think it's mostly because the marketeers haven't got to everyone yet
:-) The kernel might be e-enabled, but it's not fully
iBuzzwordcompliant.
Besides, having a *fully* XML parser/generator in the kernel is
extremely braindead, even if it's called libkernelxml ("I'm not really
quite in the kernel really") or something. What's so wrong with really
simple files being exposed to userspace? Most of these are less than a
single page of data and it's just dandy like that.
Jon.
next prev parent reply other threads:[~2005-10-02 18:53 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-02 9:41 Ahmad Reza Cheraghi
2005-10-02 9:50 ` Nick Piggin
2005-10-02 11:02 ` James Courtier-Dutton
2005-10-02 10:37 ` Nick Piggin
2005-10-02 11:57 ` Bas Westerbaan
2005-10-02 11:09 ` James Bruce
2005-10-02 13:47 ` Willy Tarreau
2005-10-03 19:21 ` Bill Davidsen
2005-10-02 18:53 ` Jon Masters [this message]
2005-10-03 15:08 ` Nix
2005-10-03 15:35 ` Al Viro
2005-10-03 19:47 ` Nix
2005-10-03 19:56 ` linux-os (Dick Johnson)
2005-10-05 21:11 ` Dave Airlie
2005-10-05 21:31 ` Nix
2005-10-05 22:57 ` Dave Airlie
2005-10-05 23:07 ` Nix
2005-10-05 23:36 ` Dave Airlie
2005-10-05 22:22 ` jmerkey
2005-10-05 23:46 ` Dave Airlie
2005-10-07 22:14 ` Matan Ziv-Av
2005-10-02 21:55 ` Martin J. Bligh
2005-10-03 4:45 ` Nick Piggin
2005-10-08 1:34 Luke Kenneth Casson Leighton
2005-10-09 15:38 ` Horst von Brand
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=35fb2e590510021153r254b7eb0haf9f9e365bed051e@mail.gmail.com \
--to=jonmasters@gmail.com \
--cc=a_r_cheraghi@yahoo.com \
--cc=jonathan@jonmasters.org \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®