OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help



   Re: [xml-dev] xml, books

[ Lists Home | Date Index | Thread Index ]

Conrad, Bill (ThomasTech) wrote:
> `	I spend most of my time developing Perl Scripts to process SGML/XML
> into and out of composition system. Most of the books I have on PERL are
> obsolete because they don't address new features of the various PERL
> packages. Most of the GUI interface I used was based on PERL Tk and UNIX.
> When I went to WIN32 GUI I couldn't find a book so I used the PERL Package
> HTML doc.

Apart from the large ones, CPAN packages rarely justify having a book about 
them. There's just too much to cover. It does seem however that ORA is on a 
mission to cover all the major parts of CPAN, so I guess they sell a bit. Apart 
from that, the Camel book ed3 is all that's needed for Perl per se. [OT bit: for 
GUI you could use Wx, it's cross-platform and looks native for the platform it's 
running on].

> 	I think that when technology changes as rapidly as it is, books are
> not the answer. I would much rather see electronic books that are updated on
> a regular basis. This is something that I would even be willing to subscribe
> to and always thought that O'Reilly & Associates would have headed in that
> direct.

Well ORA has Safari, which I found to be good. Applying the same type of system 
to books that are more regularly updated might indeed be a good idea (but I 
wouldn't want to be editor of the the permanent revolution).

> 	One Question. Is PERL or JAVA the language of choice for processing
> XML?

That's not really a question that can be properly answered. Both provide many 
tools, some similar, some different. Since I'm in a flame-bait mood I'd be 
tempted to summarize the difference as "Java has more implementations of specs 
you don't need, Perl has more implementations of things you need that aren't 
specs". But overall it seems no one has broken the problem of providing a good 
API to XML that fits many needs alike, and both Perl and Java tend to suck at 
least half of the time. I've heard good things about work being done on more 
"native" APIs, such as:


but haven't had a chance to look deeply into it yet.

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


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS