Re: Re: Best method for dynamic page generation?

What is using XSLT really buying you?

If you have the discipline to keep it clean, there is no reason to convert to XML only to have to introduce a new language and a lot of overhead. Instead you can construct the views in Perl, likely using the various templating modules to organize it.

If you do this, then you'll likely find no practical performance difference between MVC and any other approach.

Comment on Re: Re: Best method for dynamic page generation?

Replies are listed 'Best First'.
Re: Re: Re: Best method for dynamic page generation? by exussum0 (Vicar) on Jan 04, 2004 at 03:16 UTC
Well, it provides a level of modularity. If I switch from perl, to c++, to java.. there are API's that deal with turning XML to XSLT. So if I have 100 templates, and decide to switch languages, I can do so with ease. There are XSLT compilers, so you can gain some performance over ones that do a live string scan. XML isn't always slow; Using SAX, it's quite fast. I'd suggest writing a SAX implemented XML parser and see for yourself. It's almost no different from a templating engine. And as I said before, XSLT/XML aren't always THE choice. It's A choice that can take some serious consideration. New language? perl is your language, xslt would be your template language. How is it any different from using perl and HTML::Template or HTML::Mason? If your argument is against templating engines, yes, you now have HTML, (your templating engine), perl and your sql language. But that's how life is. You weigh out the advantages and make choices. Play that funky music white boy..	[reply]

Replies are listed 'Best First'.

Re: Re: Re: Best method for dynamic page generation?
by exussum0 (Vicar) on Jan 04, 2004 at 03:16 UTC

There are XSLT compilers, so you can gain some performance over ones that do a live string scan.

XML isn't always slow; Using SAX, it's quite fast. I'd suggest writing a SAX implemented XML parser and see for yourself. It's almost no different from a templating engine. And as I said before, XSLT/XML aren't always THE choice. It's A choice that can take some serious consideration.

New language? perl is your language, xslt would be your template language. How is it any different from using perl and HTML::Template or HTML::Mason? If your argument is against templating engines, yes, you now have HTML, (your templating engine), perl and your sql language. But that's how life is. You weigh out the advantages and make choices.

Play that funky music white boy..

[reply]