Sebastian Rahtz wrote:
Sebastian,My argument against XPathScript is that it ties me to Perl and AxKit. All the work I do with XSLT could be ported trivially to eg Cocoon (spit) if I had to. If I go xps, I am tied to a single supplier and framework. No lack of faith in the great axkats (surely not still kittens?), but I feel a certain duty to be as portable as possible
those that use XPathScript, like me, are not caring about portability (those who do surely use XSLT). In my case: I have a powerful tool, AxKit, a few time to create applications with it, and I know Perl: XPathScript is a God Gift! (please don't do any equivalence Matt~God here, that wouldn't be polite to religious people).
In my situation I can't care too much about portability, I need to get things done fast. To do this, I must use (partly) things I already know. That's why I use XPathScript.
Surely, I'll learn XSLT at some point. But I am grateful that XPathScript is there!
--M
--
Marco Marongiu Email: [EMAIL PROTECTED]
CRS4 Research Center Phone: +39 070 2796 336
NCS Division Fax: +39 070 2796 216
NSM Group WWW: http://bugs.unica.it:4444/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
