NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
XML as a second system (Score:1)
XML strikes me as the combined second-system effect of a
Re:XML as a second system (Score:2)
Then I would say that Piers' question isn't so much important as much as it's the wrong question to ask.
XML is a perfectly acceptable solution for one very important problem: interoperability with data exchange. There's a benefit to not creating a new binary format for each and every fragment of information we want to author, exchange, archive or share. (There's even less of a benefit to shoving all of that data into XML and ca
XML ain't great, but... (Score:2, Insightful)
Re:XML ain't great, but... (Score:3, Interesting)
Seconded. XML is an easy but lousy shot because while the horrible stuff is the part that gets the most PR (presumably because it needs it), there are lots of easy and elegant stuff being very useful under the radar.
Java on the other hand is exactly that. Take a complex Perl module implementing a horribly kludgy spec such as SOAP::Lite, and compare it in size, bloat, and ease-of-use with the supposedly state of the art Axis by the ASF.
And don't even get me started on what most Java programmer
-- Robin Berjon [berjon.com]