mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Horst von Brand <vonbrand@inf.utfsm.cl>
To: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
Cc: linux-kernel@vger.kernel.org,
	Linux Visionaries Mailing List <lvml@lists.blackwhale.net>
Subject: Re: Why no XML in the Kernel?
Date: Sun, 09 Oct 2005 12:38:15 -0300	[thread overview]
Message-ID: <200510091538.j99FcFmW005439@inti.inf.utfsm.cl> (raw)
In-Reply-To: Message from Luke Kenneth Casson Leighton <lkcl@lkcl.net>  of "Sat, 08 Oct 2005 02:34:57 +0100." <20051008013457.GR18797@lkcl.net>

Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:

[...]

>  it's a friggin sight better than contemplating XML, but it also comes
>  with a price tag: in this case, nearly 70,000 lines of library code
>  that "encapsulates" and "extracts" the data structures for you, at
>  runtime [yes, you can supply your own malloc and free routines]

70 KSLOC is a /lot/, the benefit of having that in kernel would have to be
very large to justify it. And in the frame of an operating system that
believes in flat ("just stream of bytes") interfaces throughout and
hopefully very simple tools on top ("cat", "more", "grep") that are
combined by the user to do complex stuff I just don't see it.
-- 
Dr. Horst H. von Brand                   User #22616 counter.li.org
Departamento de Informatica                     Fono: +56 32 654431
Universidad Tecnica Federico Santa Maria              +56 32 654239
Casilla 110-V, Valparaiso, Chile                Fax:  +56 32 797513


  reply	other threads:[~2005-10-10  4:29 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-08  1:34 Luke Kenneth Casson Leighton
2005-10-09 15:38 ` Horst von Brand [this message]
  -- strict thread matches above, loose matches on Subject: below --
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
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

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=200510091538.j99FcFmW005439@inti.inf.utfsm.cl \
    --to=vonbrand@inf.utfsm.cl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkcl@lkcl.net \
    --cc=lvml@lists.blackwhale.net \
    /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®