From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dave Lukes To: 9fans@cse.psu.edu Subject: Re: [9fans] don't shoot me Message-ID: <20030718165017.A1419@luchie.demon.co.uk> References: <000501c34d3f$04b5af40$2a8be793@gli.cas.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.22i Date: Fri, 18 Jul 2003 16:50:17 +0100 Topicbox-Message-UUID: fb130f5e-eacb-11e9-9e20-41e7f4b1d025 Speaking as someone who's trained/used/sworn-at XML/XSLT/XSL-FO ... > > just drop me a few words, or just [1] .. [5] ;-) [1] .. [5] :-). What Trickey said, plus. Seriously, XML has it's uses. e.g. XSL-FO may one day be a tolerable troff replacement. (Although I'd hate to be an implementor of an XSL-FO processor: the reference documents sent me to sleep in record time). On Fri, Jul 18, 2003 at 05:23:25PM +0200, Fco. J. Ballesteros wrote: > IMHO, it's text data reinvented, with some help to automate parsing. Yes, but with some tree structure and naming too. One of the "interesting" "features" I've noticed about XML is the "if the only tool you have is a hammer, everything looks like a nail" syndrome. You end up with XSLT (i.e. XML) programs manipulating XML data driven by XML configuration files and so ad infinitum. (Look at the Apache stuff, like ant for an example). (Yes, I know XSLT can _generate_ plain text, just about, but it can't _read_ it!) This disease will be familar to the Lispers out there. Cheers, Dave.