Hey, time for a shameless plug!
You can have a look at
What's wrong with Perl and XML? for my opinion on the
subject. (you may also want to check the Forum for
various, often opposite, views)
To sum it up I would just say that XML and Java are a
much better cultural fit than Perl and XML. Whitout even
discussing the technical merits of both languages for XML
processing, the kind of environment where XML is used is often
much more Java-oriented than Perl-oriented.
Which does not mean that Perl cannot be used to process XML,
PerlMonks uses XML quite a lot (User nodes info xml generator, Newest Nodes XML Generator.,
the ChatterBox client...
| [reply] |
With Java, you have several orders of magnitude more coders already, and given that Java is to programming languages as XML is to data representations, it's only natural that Java would have the good XML tools first.
ASP is a major dynamic page generation language out there, and given that XML is a good choice for representing data in back-ends, it's only natural that ASP have access to similar tools.
To be honest, I didn't realize Perl was "looked down" upon for its XML implementations. As far as I know, they're as complete and easy-to-use (perhaps easier, but that's just Perl) as any other implementation. See XML::Simple and XML::Parser. Perl isn't always the best language for the task, so perhaps some of these other tasks you're thinking about just seemed better in another language? *shrug* | [reply] |
My use of looked down upon was based on views and opinions on news and XML-centric websites that all seem to look to other languages, not from personal experience.
no offence to Perl intended!
;^)
| [reply] |
mirod wrote an article on that, viewable at xml.com. It's an interesting read.
[ar0n]
| [reply] |
Interestingly, there is a relevent article
here I found
linked from perl.com
| [reply] |