• To: Tim Bray <tbray@t...>
• Subject: Re: If XML is too hard for a programmer, perhaps he'd bebetter off as a crossing guard
• From: Robin Berjon <robin.berjon@e...>
• Date: Fri, 28 Mar 2003 17:40:01 +0100
• Cc: Dare Obasanjo <dareo@m...>, Liam Quin <liam@w...>, Uche Ogbuji <uche.ogbuji@f...>, xml-dev@l...
• In-reply-to: <3E84767B.50201@t...>
• Organization: Expway
• References: <B885BEDCB3664E4AB1C72F1D85CB29F804B7CA30@R...> <3E84767B.50201@t...>
• Reply-to: robin.berjon@e...
• User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3) Gecko/20030312

Tim Bray wrote:
> Dare Obasanjo wrote:
>> The "Desperate Perl Hacker" argument  was a bogus claim for XML 1.0 
>> because of the existence of entities and CDATA sections but is quite 
>> farcical now with the existence of the Namespaces in XML 
>> recommendation (and it's bastard spawn "QNames in content"). 
> 
> Empirically false, at two levels.  First, lots of people process XML 
> with perl (or equivalent) all the time.  Second, the real requirement 
> was to make it tractable to take a large body of document data and make 
> quick programmatic changes on it.  

Indeed, the simple fact that people are doing SAX filtering in the archetypal
Perl one-liners shows that the DPH argument has had its effect. There's work on 
making the situation even better, and the Perl 6 people are discussing very 
interesting things relating to XML.

-- 
Robin Berjon <robin.berjon@e...>
Research Engineer, Expway        http://expway.fr/
7FC0 6F5F D864 EFB8 08CE  8E74 58E6 D5DB 4889 2488

• Follow-Ups:
  • Re: If XML is too hard for a programmer, perhaps he'd be better off as a crossing guard
    • From: Liam Quin <liam@w...>

• References:
  • RE: If XML is too hard for a programmer, perhaps he'd be better off as a crossing guard
    • From: "Dare Obasanjo" <dareo@m...>
  • Re: If XML is too hard for a programmer, perhaps he'd bebetter off as a crossing guard
    • From: Tim Bray <tbray@t...>

• Prev by Date: Re: GXA specifications process
• Next by Date: Re: Re: If XML is too hard for a programmer, perhaps he'dbe better off as a crossing guard
• Previous by thread: Re: If XML is too hard for a programmer, perhaps he'd bebetter off as a crossing guard
• Next by thread: Re: If XML is too hard for a programmer, perhaps he'd be better off as a crossing guard
• Index(es):
  • Date
  • Thread