Sebastian Rahtz wrote:
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
I'm unsure about that argument. XPS ties you to Perl, but not to AxKit as it does have an offline version (it can prolly be used in CGI, vanilla modperl, etc).

So basically it's about having a Perl compiler vs having an XSLT processor. Surely, both are about as portable ;)

Still an axkitten, as far as I'm concerned...

--
Robin Berjon <[EMAIL PROTECTED]>
Research Engineer, Expway http://expway.fr/
7FC0 6F5F D864 EFB8 08CE 8E74 58E6 D5DB 4889 2488


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to