9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: David Leimbach <leimy2k@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] xml
Date: Wed, 30 Jun 2010 11:25:46 -0700	[thread overview]
Message-ID: <AANLkTik99pDEQkNMoXU0LX6c6nJVe1yONckv9CFOpWzt@mail.gmail.com> (raw)
In-Reply-To: <AANLkTikNZaoL7xnabaz3Si6yz-cMNkvXTB0xoUPYVjMs@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1959 bytes --]

On Wed, Jun 30, 2010 at 7:47 AM, hugo rivera <uair00@gmail.com> wrote:

> Now that I had a closer look to xml files, I think I get the main idea.
> From my point of view, xml doesn't seem so bad after all (please,
> please, this is just an uninformed opinion) but perhaps in the future
> I'll be able to see its defects.
>
> --
> Hugo
>
>
What XML buys you is a bunch of tools that already work for about half of
what you'd want a language tool to do.  By this I mean there's parsers
already written, and lots of libraries to examine the tags at different
levels in a hierarchy or stream of XML data.

You still have to define the meaning of each tag, attribute and tagged text.
 For validation of documents in XML there's other XML technologies like
Schemas you can use, or you could describe the valid set of tags in a DTD.

To add to the madness you can write XML files that translate XML files to
other files (possibly other XML files) in an XML defined language called
XSLT.  XSLT is a bit like writing in a functional programming language with
the worst syntax possible :-).

The reason I say "worst syntax possible" is that the amount of typing you'll
do to express something simple in XML is pretty excessive.

Eventually you'll find that the entire world became a nail for the XML
hammer and that things like SOAP, XML-RPC, are just not very good due to the
fact that sending XML documents on a wire for simple RPC calls is grossly
inefficient, and there's a lot better technology out there for these sorts
of things.

That said, XML is still here, and you kind of have to learn to play ball
with it.  I just had a discussion with a coworker about a configuration
language for a management project here at work and had to argue in XML's
defense (customers will more easily understand and be able to accept an XML
language than whatever new cute DSL we come up with).

I feel like I need a shower now.

Dave

[-- Attachment #2: Type: text/html, Size: 2517 bytes --]

  reply	other threads:[~2010-06-30 18:25 UTC|newest]

Thread overview: 77+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-28 16:19 hugo rivera
2010-06-28 16:55 ` Russ Cox
2010-06-28 17:06 ` Ethan Grammatikidis
2010-06-28 18:26   ` Rob Pike
2010-06-28 18:31     ` David Leimbach
2010-06-28 18:40       ` Rob Pike
2010-06-28 19:06         ` erik quanstrom
2010-06-28 19:14           ` Corey Thomasson
2010-06-30 14:47             ` hugo rivera
2010-06-30 18:25               ` David Leimbach [this message]
2010-06-30 18:43                 ` ron minnich
2010-06-30 19:54                   ` Pietro Gagliardi
2010-06-30 20:04                     ` Corey Thomasson
2010-06-30 20:21                       ` erik quanstrom
2010-06-30 20:53                         ` Wes Kussmaul
2010-07-01 15:06                           ` Ethan Grammatikidis
2010-07-01 17:12                             ` Russ Cox
2010-07-01 17:43                               ` Bakul Shah
2010-07-01 18:37                                 ` Jorden M
2010-07-01 18:49                                   ` Rob Pike
2010-07-01 19:33                                     ` Bakul Shah
2010-07-01 19:34                                     ` Jorden M
2010-07-02 10:45                                       ` roger peppe
2010-06-30 20:07                     ` LiteStar numnums
2010-06-30 18:59                 ` LiteStar numnums
  -- strict thread matches above, loose matches on Subject: below --
2010-07-03 15:51 Dean Bittner
2007-05-21 16:57 [9fans] XML ron minnich
2007-05-21 17:08 ` W B Hacker
2007-05-21 17:11 ` Roman Shaposhnik
2007-05-21 17:27   ` W B Hacker
2007-05-21 17:37     ` Francisco J Ballesteros
2007-05-22 10:47       ` Charles Forsyth
2007-05-22 11:31         ` erik quanstrom
2007-05-25 15:03         ` David Leimbach
2007-05-25 15:08           ` erik quanstrom
2007-05-25 17:02           ` Charles Forsyth
2007-05-25 17:32             ` Francisco J Ballesteros
2007-05-25 18:15               ` ron minnich
2007-05-25 19:58                 ` Uriel
2007-05-25 22:11                 ` erik quanstrom
2007-05-25 19:35               ` Steve Simon
2007-05-25 20:36                 ` Francisco J Ballesteros
2007-05-25 18:30         ` ozan s. yigit
2007-05-25 20:23           ` Charles Forsyth
2007-05-21 17:33   ` ron minnich
2007-05-21 20:18     ` David Leimbach
2007-05-21 20:25       ` erik quanstrom
2007-05-22  4:13         ` lucio
2007-05-21 18:17   ` erik quanstrom
2007-05-21 18:29     ` Uriel
2007-05-21 18:21   ` Uriel
2007-05-22  1:25     ` LiteStar numnums
2007-05-21 18:26   ` Skip Tavakkolian
2007-05-21 18:39     ` Jack Johnson
2007-05-21 18:48       ` Uriel
2007-05-21 19:26       ` Skip Tavakkolian
2007-05-21 20:17   ` David Leimbach
2007-05-21 22:34   ` Steve Simon
2007-05-21 17:32 ` Bakul Shah
2007-05-21 18:23 ` matt
2007-05-21 18:34 ` Geoffrey Avila
2007-05-21 18:41   ` Uriel
2007-05-21 19:27     ` Geoffrey Avila
2007-05-22 22:24       ` Roman Shaposhnik
2007-05-22  4:08     ` lucio
2007-05-21 23:29   ` W B Hacker
2007-05-21 23:34     ` erik quanstrom
2007-05-22 14:02       ` Wes Kussmaul
2007-05-22 14:03         ` erik quanstrom
2007-05-22 14:55           ` Bruce Ellis
2007-05-22 15:05             ` Jack Johnson
2007-05-23  7:12             ` Lluís Batlle
2007-05-23  8:11               ` Lluís Batlle
2007-05-23  8:29                 ` lucio
2007-05-22 15:22           ` Wes Kussmaul
2007-05-22 14:53         ` Jack Johnson
2007-05-22  9:53   ` Charles Forsyth

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=AANLkTik99pDEQkNMoXU0LX6c6nJVe1yONckv9CFOpWzt@mail.gmail.com \
    --to=leimy2k@gmail.com \
    --cc=9fans@9fans.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;
as well as URLs for NNTP newsgroup(s).