From: Linas Vepstas <linasvepstas@gmail.com>
To: Andy Wingo <wingo@pobox.com>
Cc: guile-user@gnu.org
Subject: Re: Web services on guile
Date: Sun, 23 May 2010 20:17:26 -0500 [thread overview]
Message-ID: <AANLkTimKk4xmNsmamvzw_vRtbmWo-zOVZQIiJbqtWzkY@mail.gmail.com> (raw)
In-Reply-To: <m3wruuuxmr.fsf@pobox.com>
On 23 May 2010 16:16, Andy Wingo <wingo@pobox.com> wrote:
> On Sun 23 May 2010 11:25, Sascha Ziemann <ceving@googlemail.com> writes:.
>
> I would agree, FWIW. I wanted to implement XML-RPC at one point in
> tekuti, but decided not to after looking at the spec. An s-expression
> serializer/unserializer is fairly simply to write, you avoid
> distribution problems that way, and you also avoid impedance mismatches.
I've sometimes liked to say that whoever invented XML had
gotten an F in college when studying LISP, although perhaps
they never studied lisp at all. I've never really figured out
whether I'm being a troll when I say that, or not.
FWIW, I've worked with a data exchange format that has
both an XML and a scheme/guile version. Running the scheme
version of the dataset through guile-1.8 (and passing it into the
C++ system that needs the data) is 3x faster than running
it through the libxerces C++ XML parser. (I've got detailed
speeds & feeds numbers if anyone cares) The website
for libxerces says its "high performance, modular, scalable",
which is either a bald lie hallucinated by the maintainers,
or it's true, and a testament to how slowwww XML
fundamentally is.
If you want to be vaguely standards-interoperable, JSON is
worth a look, its pretty simple & yet powerful too. Never used
it in any data-intense situation, though.
--linas
next prev parent reply other threads:[~2010-05-24 1:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-22 20:20 Web services on guile Romel R. Sandoval Palomo
2010-05-23 9:25 ` Sascha Ziemann
2010-05-23 21:16 ` Andy Wingo
2010-05-24 1:17 ` Linas Vepstas [this message]
2010-05-25 14:48 ` Romel Sandoval
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AANLkTimKk4xmNsmamvzw_vRtbmWo-zOVZQIiJbqtWzkY@mail.gmail.com \
--to=linasvepstas@gmail.com \
--cc=guile-user@gnu.org \
--cc=wingo@pobox.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).