c*******9
发帖数: 9032 | 1 这些评论比较有趣
http://lambda-the-ultimate.org/node/1222
Several problems with XML; IT industry on acid trip.
XML has several problems. It is slow to parse, it can result in big files,
it only describes what the data are and not how to handle them etc. But it
is a step in the right direction: we need to have a way to make programs
interact based on a common protocol. In other words, we have a problem (
interaction of programs), the correct approach (a common protocol) with a
wrong solution (xml).
Maybe if every computer came with LISP (or something similar), computers
could use that as a protocol instead of xml or any other protocol. If you
thing about it, there are lots of protocols invented to solve the same
problems (or the same nature of problems).
Take html for example; any HTML document can be represented with LISP lists.
In fact, if we had LISP data sent over the network, we would have less data
to send over (as a LISP program can be sent as a list of tokens); we wouldn
't have to invent javascript, dhtml or ajax, as LISP data are both code and
data at the same time. We wouldn't have to use SQL, since database schemas
could be represented by LISP lists. We wouldn't have to invent SOAP, since
LISP data could be used for sending requests over the network; we wouldn't
have to invent OpenDoc or document formats, as LISP lists are more than
sufficient to describe any format. We wouldn't have postscript, as
postscript is nothing more than a bunch of instructions ala xml/LISP. We
wouldn't have command line interpreters, since LISP can also play that role.
We wouldn't need COM or CORBA. And on top of that, development could be
bottom-to-top instead of top-to-bottom, since LISP development is usually
interactive.
And on top of all these things, we also have managers that are clueless in
technical details, and they insist to use XML because it will look good on
the company's resume... |
|
